Hi,
Its been a while but there is a new odbc driver at
http://www.insightdist.com/psqlodbc. This one has some significant
enhancements including a parse SQL statements option and a port to the
unix iodbc of the source code.
The SQL parsing option helps a great deal with the Borland DBExplorer
which runs queries and expects detailed information (precision,
nullability, aliases, etc.) on the result set before fetching any data.
It also uses this method in the data dictionary import. When the parser
encounters something it can't handle (like expressions or functions in a
column), it will fallback on executing the statement as before.
The parsing option, although fairly advanced, represents the first cut
of driver-side parsing. I have more improvements to come on this later.
Also, Dave revamped our website so check that out.
Byron
version.txt date: 7/6/98 version: 06.30.0247
---------------------------------------------------------------------
This file describes changes and or fixes since the last update.
NEW FEATURES:
1. Added SQL statement parsing ability to the driver. This allows the driver
to return information about column precision, nullability, length, aliases,
etc., since Postgres doesn't return this info in a query. This also
improves performance on applications that execute queries just for the
purpose of finding out about the result data instead of actually retrieving
it.
Borland will get a big boost from this option. The Import Dictionary
function should now properly report sizes of varchars. Plus, you can
execute most queries in DBExplorer and get the real sizes of columns.
The parsing statements option is enabled on the Advanced Driver options
dialog.
2. Return the quoted identifer character as a quote instead of blank. This
allows you many tools to use column and table names that have spaces and
other characters contained in them.
3. This source release contains the driver ported for Unix IODBC. See the
README.Linux file for more information.
BUG_FIXES:
1. Return something (just regular tables) for SQLTables if no table types
are supplied. This may help Cold Fusion applications.
2. Allow TXN_ISOLATION to be set as a connect option.