ODBC API Support
The following table lists the ODBC API functions supported by the Relational Interface and the ODBC support level. For detailed information on the ODBC API, refer to the Microsoft ODBC documentation.
Table 1
PSQL Support for ODBC API Functions  
ODBC Function
ODBC Support Level
SQLAllocHandle
Core
SQLBindCol
Core
SQLBindParameter
Core
SQLBrowseConnect
Level 1
SQLBulkOperations
Level 1
SQLCancel
Core
SQLCloseCursor
Core
SQLColAttribute
Core
SQLColumnPrivileges
Level 2
SQLColumns
Core
SQLConnect
Core
SQLCopyDesc
Core
SQLDataSources
Core
SQLDescribeCol
Core
SQLDescribeParam
Level 2
SQLDisconnect
Core
SQLDriverConnect
Core
SQLDrivers
Core
SQLEndTran
Core
SQLExecDirect
Core
SQLExecute
Core
SQLExtendedFetch
Core
SQLFetch
Core
SQLFetchScroll
Core
SQLForeignKeys
Level 2
SQLFreeHandle
Core
SQLFreeStmt
Core
SQLGetConnectAttr
Core
SQLGetCursorName
Core
SQLGetData
Core
SQLGetDescField
Core
SQLGetDescRec
Core
SQLGetDiagField
Core
SQLGetDiagRec
Core
SQLGetEnvAttr
Core
SQLGetFunctions
Core
SQLGetInfo
Core
SQLGetStmtAttr
Core
SQLGetTypeInfo
Core
SQLMoreResults
Level 1
SQLNativeSql
Core
SQLNumParams
Core
SQLNumResultCols
Core
SQLParamData
Core
SQLPrepare
Core
SQLPrimaryKeys
Level 1
SQLProcedureColumns
Level 1
SQLProcedures
Level 1
SQLPutData
Core
SQLRowCount
Core
SQLSetConnectAttr
Core
SQLSetCursorName
Core
SQLSetDescField
Core
SQLSetDescRec
Core
SQLSetEnvAttr
Core
SQLSetPos
Level 1
SQLSetStmtAttr
Core
SQLStatistics
Core
SQLTablePrivileges
Level 2
SQLTables
Core
Exceptions to ODBC API Support
The following section contains details on the exceptions to ODBC API support.
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.
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.
SQLGetTypeInfo
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 Supported Data Types for a list of supported ODBC data types.
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 PSQL database engine.
bb
Minor version
The minor version of the 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 Actian Corporation 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
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 in SQL Engine Reference.