ODBC Support

SQLGetTypeInfo generates a list of native data type names (type_name) specified by the relational interface. For example, SQL_CHAR is mapped to CHARACTER. Use the names which are returned from this function for the data type names for columns in a CREATE TABLE or ALTER TABLE statement or for parameters for procedures or declared variables in procedures and triggers.

See also Pervasive PSQL Data Types and Equivalent ODBC Data Types for a list of supported ODBC data types.

SQLSpecialColumns

The relational interface uses unique indexes as the optimal set of columns that uniquely identifies a row in the table. When a new row is inserted, the relational interface does not return the values for IDENTITY columns. You may determine the value for an IDENTITY column through the use of the @@IDENTITY variable. See @@IDENTITY.

SQLGetData

If your application calls SQLGetData to return data into an SQL_C_NUMERIC structure, the ODBC standard specifies that the SQL_DESC_SCALE field is set to zero and the SQL_DESC_PRECISION field uses the driver-defined precision.

Pervasive PSQL use the values for scale and driver-defined precision as defined in the metadata. Consider the following example, in which scale is set to two.

CREATE TABLE testnum (col1 NUMERIC(10,2))

INSERT INTO testnum VALUES (10.34)

SELECT * FROM testnum

The SELECT statement returns 10.34, not 10.00.

SQLGetInfo

The relational interface returns identical values for SQL_DRIVER_VER and SQL_DBMS_VER. This version value is returned in the following format:

aa.bb.cccc ddd

This value can be interpreted as four components as explained in the following table:


Part	Value	Description
aa	Major version	The major version of the Pervasive PSQL database engine.
bb	Minor version	The minor version of the Pervasive PSQL database engine, which is typically updated in a service pack.
cccc	Build number	The build further specifies the release by marking the time at which Pervasive Software generated the release.
ddd	Point build	A minor update to the build. The build number and point build uniquely identify a product release created at a specific time.

The following table summarizes the expected format of other values typically returned by SQLGetInfo. The values are examples only.


Item	Example Value
SQL_DRIVER_NAME	W3ODBCCI.DLL
SQL_DRIVER_VER	10.00.0147 012
SQL_DRIVER_ODBC_VER	03.51
SQL_DBMS_NAME	Pervasive.SQL
SQL_DBMS_VER	10.00.0147 012
SQL_ODBC_VER	03.52.0000
SQL_ODBC_API_CONFORMANCE	SQL_OAC_LEVEL2
SQL_ODBC_INTERFACE_CONFORMANCE	SQL_OIC_LEVEL2

ODBC Attribute Support

The relational interface provides ODBC v3.51 attribute support, with the following exceptions.

Exceptions to ODBC Attribute Support

Statement Attribute Support

The following table lists the exceptions to ODBC statement attribute support:

Table 21

Exceptions to ODBC Statement Attribute Support

fOption (numerical value)

Comments

SQL_ATTR_QUERY_TIMEOUT (0)

Supported through SQLSetStmtAttr and SQLSetConnectAttr. Applies only to SQLExecDirect, SQLExecute, SQLFetch, and SQLExtendedFetch. Does not apply to DDL statements.

SQL_ATTR_METADATA_ID (10014)

The default value is SQL_FALSE. Pervasive ODBC Driver does not allow setting this attribute's value to SQL_TRUE.

SQL_ATTR_ENABLE_AUTO_IPD (15)

The default value is SQL_TRUE. Pervasive ODBC Driver does not allow setting this attribute value to SQL_FALSE.

SQL_ATTR_PARAM_BIND_TYPE (18)

Only SQL_PARAM_BIND_BY_COLUMN is supported.

Connection Attribute Support

The following table lists the exceptions to ODBC Connection Attribute support:

Table 22

Exceptions to ODBC Connection Attribute Support

fOption

Comments

SQL_ATTR_AUTO_IPD

The default value is SQL_TRUE. The Pervasive ODBC Driver does not allow setting this attribute value to SQL_FALSE.

SQL_ATTR_METADATA_ID

The default value is SQL_FALSE. The Pervasive ODBC Driver does not allow setting this attribute's value to SQL_TRUE

SQL_ATTR_CONNECTION_TIMEOUT

The default value is 0. No other value is supported.

ODBC Descriptor Field Support

The relational interface provides ODBC v3.51 descriptor field support, with the following exceptions.

Exceptions to ODBC Descriptor Support

The following table lists the exceptions to ODBC descriptor field support:

Table 23

Exceptions to ODBC Descriptor Support

fOption

Comments

SQL_DESC_BIND_TYPE

For application parameter descriptors (APDs), only SQL_BIND_BY_COLUMN is supported.

SQL_DESC_ROWVER

See Exceptions to ODBC Interface Support.

Descriptor Fields and Bitness Values

Note that some of the descriptor fields that can be set through the various ODBC SQLSet and SQLGet functions have been changed to accommodate 64-bit values while others are still 32-bit values. If you are using the 64-bit ODBC driver, ensure that you use the appropriate sized variable when setting and retrieving these fields. For more information, refer to the Microsoft ODBC documentation. See especially http://msdn.microsoft.com/en-us/library/ms716287%28VS.85%29.aspx.

A point of clarification is that SQL_ROWSET_SIZE is supported by both SQLGetStmtOption and SQLGetStmtAttr. If you are using the 64-bit ODBC driver and you call either SQLGetStmtOption or SQLGetStmtAttr, a 64-bit value is returned in *ValuePtr when that attribute parameter is set to SQL_ROWSET_SIZE.

SQLSetStmtOption Options

The section discusses the Pervasive PSQL support for the following SQLSetStmtOption options:

•

•

•

•

•