 | DTI Programmer's Guide (v10) |  |
|
The following describes the structures used in the Distributed Tuning Interface. Each structure grouping details the type of structures included and any noteable settings or arguments that may be required. Structures are stored in the following header files:
For detailed information specific to each structure, refer to the corresponding header file for that structure.
The following lists the structures included in CONFIG.H. For detailed information about any of these structures, refer to the config header file.
The following lists the structures included in DDFSTRCT.H. For detailed information about any of these structures, refer to the ddf header file.
B_FLAG_TRUE_NULLABLE = 64Table is true nullable. When the table is created, a one byte null indicator is added before each column that is nullable.
B_FLAG_CASE_SENSITIVE = 1Column values are case sensitive on comparisons and as part of index segments.
B_FLAG_NULLABLE = 4If the table is created as true nullable, then a one byte null indicator column is added before the column value to indicate whether the column value is null.
COLUMNMAP DataType can take the following values:
B_TYPE_STRING = 0, B_TYPE_INTEGER = 1, B_TYPE_FLOAT = 2, B_TYPE_DATE = 3, B_TYPE_TIME = 4, B_TYPE_DECIMAL = 5, B_TYPE_MONEY = 6, B_TYPE_LOGICAL = 7, B_TYPE_NUMERIC = 8, B_TYPE_BFLOAT = 9, B_TYPE_LSTRING = 10, B_TYPE_ZSTRING = 11, B_TYPE_NOTE = 12, B_TYPE_LVAR = 13, B_TYPE_BINARY = 14, B_TYPE_AUTOINC = 15, B_TYPE_BIT = 16, B_TYPE_NUMERSTS = 17, B_TYPE_NUMERSA = 18, B_TYPE_CURRENCY = 19, B_TYPE_TIMESTAMP = 20, B_TYPE_BLOB = 21, B_TYPE_GDECIMAL = 22, B_TYPE_WSTRING = 25, B_TYPE_WZSTRING = 26, B_TYPE_GUID = 27, B_TYPE_DATETIME = 30
B_FLAG_DUPLICATES = 1Duplicates allowed in index.
B_FLAG_MODIFIABLE = 2Index is modifiable.
B_FLAG_SORT_DESCENDING = 64Sort index descending.
B_FLAG_PARTIAL = 512Index is partial. Partial Index flags on segments that are not the last segment in the index, are ignored. Partial Indexes only apply to the last segment in an index.
Note the following differences between the new TABLESTAT2 structure and the TABLESTAT structure:
Pervasive PSQL clients can still make PvGetTableStat calls to the database engine. The database engine converts the reply message to a TABLESTAT2 structure or to a TABLESTAT structure as required based on the version of the client.
A Pervasive PSQL v10 client determines the version of the database engine to which the client is connected. If the database engine version is prior to Pervasive PSQL v10, then PvGetTableStat2 returns a TABLESTAT structure and sets the value returned for pageCompression to 0.
The following lists the structures included in MONITOR.H. For detailed information about any of these structures, refer to the monitor header file.
|
Chapter contents
Prev topic: Error Messages
|