ODBC Driver for PostgreSQL
This package contains the ODBC (Open DataBase Connectivity) driver and
sample configuration files needed for applications to access a
PostgreSQL database using ODBC.
- Developed at server:database:postgresql
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Slowroll:Base:1/psqlODBC && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
psqlODBC-internal.patch | 0000000799 799 Bytes | |
psqlODBC.changes | 0000017476 17.1 KB | |
psqlODBC.spec | 0000002518 2.46 KB | |
psqlodbc-12.02.0000.tar.gz | 0000937847 916 KB |
Revision 27 (latest revision is 31)
Dominique Leuenberger (dimstar_suse)
accepted
request 811346
from
Michael Vetter (jubalh)
(revision 27)
- Update to 12.02.0000: * Add a new *Display Optional Error Message* option. This option allows to display error messages other than primary one. Also add documentaition about the option and *Numeric as* option. * Handle notice messages in libpq_bind_and_exec(). Sets and resets a notify receiver around PQexecParams() or PQexecPrepared(). * Ignore PQtransactionStatus PQTRANS_ACTIVE in LIBPQ_update_transaction_status(). PQTRANS_ACTIVE isn't a transaction status. * Improve execution of parameterized SQL statements with arrays of parameters by sending chunks of SQL statements. If SQL_ATTR_CURSOR_TYPE of an statement is SQL_CURSOR_FORWARD_ONLY, SQL_ATTR_CONCURRENCY is SQL_CONCUR_READ_ONLY and extended protocol isn't used, the batch execution of the statement is possible. A new option Batch Size was introduced for such cases. Batch Size: Split an array (of parameters) into chunks of Batch Size to execute statements. The last chunk may contain less than Batch Size elements. Setting 1 to this option forces the current one by one execution. Also turn off use_server_side_prepare option temporarily when batch executuion is possible. * Change SC_execute() so that it returns a return code which is not affetced by the preceding results. It's necessary for batch execution with arrays of parameters. * Add a new option IgnoreTimeout. * Some tools issue issue SQLSetStmtAttr(.., SQL_ATTR_QUERY_TIMEOUT,,) internally and sometimes it's difficult for users to change the
Comments 0