From: Byron Nikolaidis <byronn@insightdist.com>
To: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgreSQL.org>
Cc: Benoit Foucher <bfoucher@pratique.fr>
Cc: Stephen Davies <scldad@sdc.com.au>
Cc: Jose' Soares Da Silva <sferac@bo.nettuno.it>
Cc: Hannu Krosing <hannu@trust.ee>
Cc: Tom Ivar Helbekkmo <tih+mail@Hamartun.Priv.NO>
Cc: Sbragion Denis <infotecn@tin.it>
Cc: Dario Fumagalli <dfumagalli@art-media.it>
Cc: Olaf Mittelstaedt <mstaedt@va-sigi.va.fh-ulm.de>
Cc: Paul Lisewski <paull@techone.com.au>
Cc: Christopher Luk <wluk@hkcccc.org>
Cc: Aleksey Demakov <avd@avd.garsib.ru>
Cc: Tony Cowderoy <tony@nthfen.demon.co.uk>
Subject: NEW ODBC DRIVER
Date: Fri, 08 May 1998 12:35:19 -0400
Message-ID: <35533446.92762625@insightdist.com> (raw)
Hello all,
There is a new odbc driver (version 6.30.0237) and source code at our
website (http://www.insightdist.com/psqlodbc). This one contains some
bug fixes AND alot of setup options! You can now configure the driver
more closely to match your needs hopefully. Please click on the version
link and/or the "dialog boxes" link for more detailed information. Some
quick highlights are:
- By democratic vote, uses ISO datestyle, period! Automatically sets
this datestyle to backend on connection.
- Advanced options for Driver and Datasource (and lots of them).
- Ability to control whether cursors are used, thus emulating the old
driver/libpq behavior.
- Ability to control how unknown sizes are reported: "Longest" emulates
old driver/libpq behavior.
- Recognizing Unique indexes is a driver option.
- Some data type mappings and data type sizes are configurable.
- SQLExtendedFetch implemented when not using cursors.
There is also a "Defaults" button to set all these options back to
optimum settings.
Note, there are performance issues involved with not using cursors,
since the driver must suck down all the rows in the result set.
However, there are some advantages when it comes to updating tables
since the tables are not kept locked by the backend. If you are having
problems with locked tables or the driver hanging, try setting Use
Cursors to false. This is a workaround until whenever the backend
locking improves. Also, when not using cursors, the sizes of character
data types varchar and text can be known since all the tuples are
retrieved in the result set. So if you set the option "Longest" on the
Advanced Options (Driver), this will be possible.
Feedback on this new driver is appreciated.
Regards,
Byron.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: byronn@insightdist.com, bfoucher@pratique.fr, scldad@sdc.com.au, sferac@bo.nettuno.it, hannu@trust.ee, tih+mail@Hamartun.Priv.NO, infotecn@tin.it, dfumagalli@art-media.it, mstaedt@va-sigi.va.fh-ulm.de, paull@techone.com.au, wluk@hkcccc.org, avd@avd.garsib.ru, tony@nthfen.demon.co.uk
Subject: Re: NEW ODBC DRIVER
In-Reply-To: <35533446.92762625@insightdist.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox