2.3 EDB-ODBC Connection Properties
2 EDB-ODBC Overview : 2.3 EDB-ODBC Connection Properties
The following table describes the connection properties that you can specify through the dialogs in the graphical connection manager tools, or in the odbc.ini file that defines a named data source. The columns identify the connection property (as it appears in the ODBC Administrator dialogs), the corresponding keyword (as it appears in the odbc.ini file), the default value of the property, and a description of the connection property.
Database system. Either EnterpriseDB or PostgreSQL Use the Protocol option to specify rollback behavior. 0 - Don't rollback1 - Rollback the transaction2 - Rollback the statement Specifies that the connection is READONLY If enabled, the driver reports system tables in the result set of the SQLTables() function. If enabled, the SQLColumns() function reports the OID column. If enabled, the SQLStatistics() function reports that a unique index exists on each OID column. If enabled, the SQLStatistics() function will report unique indexes. If not enabled, the SQLStatistics() function reports that indexes allow duplicate values. If enabled, the driver will use server-side cursors. To enable UseDeclareFetch, specify a value of 1; to disable UseDeclareFetch, specify a value of 0 If enabled, the driver parses simple SELECT statements when you call the SQLNumResultCols(), SQLDescribeCol() or SQLColAttributes() functions. If enabled, the SQLCancel() function will call SQLFreeStmt(SQL_Close) on your behalf. If enabled, the driver records its work in a log file. On Windows, the file name is C:\mylog_<process-id>; on Linux the file name is /tmp/mylog_<username><process-id>.log Determines how the SQLDescribeCol() そして SQLColAttributes() functions compute the size of a column. Specify 0 to force the driver to report the maximum size allowed for the type; specify 1 to force the driver to report an unknown length or 2 to force the driver to search the result set to find the longest value. Do not specify 2 if you have enabled UseDeclareFetch If enabled, the driver treats TEXT columns as if they are of type SQL_LONGVARCHAR. If disabled, the driver treats TEXT columns as SQL_VARCHAR values. If enabled, the driver treats values of unknown type as SQL_LONGVARCHAR values. If unchecked, the driver will treat values of unknown type as SQL_VARCHAR values. By default, values of unknown type are treated as Y values. If enabled, the driver treats BOOL columns as SQL_CHAR values. If disabled, BOOL columns are treated as SQL_BIT values. If enabled, the driver treats VARCHAR そして BPCHAR values longer than MaxVarCharSize as SQL_LONGVARCHAR values If TextAsLongVarChar is on, the driver reports TEXT values are MaxLongVarcharSize bytes long.If UnknownAsLongVarChar is on, columns of unknown type are MaxLongVarcharSize bytes long; otherwise, they are reported to be MaxVarcharSize bytes in length. Determines the number of rows fetched by the driver when UseDeclareFetch is enabled. Use the SysTablePrefixes field to specify a semi-colon delimited list of prefixes that indicate that a table is a system table. By default, the list contains dd_; If enabled, the SQLRowCount() function will return a single, cumulative row count for the entire array of parameter settings for an INSERT statement. If disabled, an individual row count will be returned for each parameter setting. By default, this option is disabled. The LF<->CR/LF conversion option instructs the driver to convert line-feed characters to carriage-return/line-feed pairs when fetching character values from the server and convert carriage-return/line-feed pairs back to line-feed characters when sending character values to the server. By default, this option is enabled. Permits positioned UPDATE そして DELETE operations using the SQLSetPos() or SQLBulkOperations() functions. If enabled, the driver treats BYTEA values as if they are of type SQL_LONGVARBINARY. If disabled, BYTEA values are treated as SQL_VARBINARY values. If enabled, the driver treats BYTEA values as if they are large objects. The Row Versioning option specifies if the driver should include the xmin column when reporting the columns in a table. The xmin value is the ID of the transaction that created the row. You must use row versioning if you plan to create cursors where SQL_CONCURRENCY = SQL_CONCUR_ROWVER Determines driver behavior if you try to retrieve information about a query without executing the query. If あり, the driver declares a cursor for the query and fetches the meta-data from the cursor. If No, the driver executes the command as soon as you request any meta-data. TrueIsMinus1 tells the driver to return BOOL values of TRUE as -1. If this option is not enabled, the driver will return BOOL values of TRUE as 1. The driver always returns BOOL values of FALSE as 0 If enabled, the driver uses the PREPARE そして EXECUTE commands to implement the Prepare/Execute model. The value of BI determines how the driver treats BIGINT values:If -5 as a SQL_BIGINT,If 2 as a SQL_NUMERIC,If 8 as a SQL_DOUBLE,If 4 as a SQL_INTEGER,If 12 as a SQL_VARCHAR,If 0 (on an MS Jet client), as a SQL_NUMERIC,If 0 on any other client, as a SQL_BIGINT 0x1 - Forces the output of short-length formatted connection strings. Specify this option if you are using the MFC CDatabase class.0x2 - Allows MS Access to recognize PostgreSQL's serial type as AutoNumber type.0x4 - Return ANSI character types for the inquiries from applications. Specify this option for applications that have difficulty handling Unicode data.0x8 - If set, NULL dates are reported as empty strings and empty strings are interpreted as NULL dates on input.0x10 - Determines if SQLGetInfo returns information about all tables, or only accessible tables. If set, only information is returned for accessible tables.0x20 - If set, each SQL command is processed in a separate network round-trip, otherwise, SQL commands are grouped into as few round-trips as possible to reduce network latency. If libpq (and its dependencies) are installed in the same directory as the EDB-ODBC driver, enabling SSL Mode allows you to use SSL and other utilities. If enabled, calls to SQL_TABLES only include user-accessible tables.
2 EDB-ODBC Overview : 2.3 EDB-ODBC Connection Properties