PvCreateDatabase2()

PvCreateDatabase2()

Creates a database by adding an entry to dbnames.cfg file. This function is the same as PvCreateDatabase() except that the database code page is also specified.

Header File: catalog.h (See also Header Files)

Function First Available In Library: w3dbav90.dll (Windows), libpsqldti.so (Linux), libpsqldti.dylib (OS X) (See also Link Libraries)

BTI_API PvCreateDatabase2(

BTI_LONG hConnection,

BTI_CHAR_PTR dbName,

BTI_CHAR_PTR dictPath,

BTI_CHAR_PTR dataPath,

BTI_ULONG dbFlags,

BTI_LONG dbCodePage);

Connection handle that identifies the server. Connection handles are obtained with the PvConnectServer() function.

Name of the database.

Dictionary path.

Data path. Pass an empty string to use the default data path (that is, the same as the dictionary path)

If you want to create a database that consists of MicroKernel Engine data files located in multiple paths, specify this parameter as a semicolon (;) delimited list. For example: C:\data\path1;C:\data\path2

Database flags, which can be a combination of the P_DBFLAG_ constants.

P_DBFLAG_RI (enforce integrity constraints, including referential integrity and triggers)

P_DBFLAG_BOUND (create DDF files and stamp the database name on the dictionary files so only that database can use them. If the database is not bound, then several databases can use the same dictionary file set.) If trying to create a bound database and you want to bind to DDF files that already exist, specify both P_DBFLAG_CREATE_DDF and P_DBFLAG_BOUND.

P_DBFLAG_CREATE_DDF (create DDF files. The directory specified for dictPath has to exist.)

P_DBFLAG_DBSEC_AUTHENTICATION (use database security authentication, Mixed security policy. See Btrieve Security Policy.)

P_DBFLAG_DBSEC_AUTHORIZATION (use database security authorization, Database security policy. See Btrieve Security Policy.)

P_DBFLAG_LONGMETADATA (use V2 metadata. See Metadata Version.)

For databases on Windows platforms, a number indicating the code page for database data and metadata strings.

For databases on Linux and OS X distributions, one of the following to indicate the code page for database data and metadata strings:

•

P_DBCODEPAGE_UTF8

•

P_DBCODEPAGE_EUCJP

•

P_DBCODEPAGE_ISO8859_1

For databases on Windows, Linux, and OS X, a value of zero can also be used.

Zero indicates legacy behavior. That is, no code page is specified, which uses the operating system (OS) encoding on the server machine. See also Database Code Page in PSQL User's Guide.

Note: The database engine does not validate the encoding of the data and metadata that an application inserts into a database. The engine assumes that all data was entered using the encoding of the server or the client as explained in Database Code Page and Client Encoding in Advanced Operations Guide.


P_OK	The operation was successful.
P_E_INVALID_HANDLE	Invalid connection handle.
P_E_NULL_PTR	Call with NULL pointer
P_E_ACCESS_RIGHT	Insufficient access right for the operation
P_E_DICTIONARY_ALREADY_EXISTS	Cannot create dictionary because it already exists.
P_E_SHARED_DDF_EXIST	The dictionary path is being used by another database.
P_E_DUPLICATE_NAME	Named database already exists on the server.
P_E_FAIL	Failed for other reasons.

The following preconditions must be met:

•

DTI session started by calling PvStart().

•

Connection established by PvConnectServer() or if you are performing the operation on a local machine, P_LOCAL_DB_CONNECTION may be used as the connection handle.

Btrieve Security Policy and Metadata Version

See Btrieve Security Policy and Metadata Version, respectively.

PvConnectServer()

PvDropDatabase()

PvGetDbCodePage()

PvModifyDatabase2()