Everyone,
Recently, I had to research a problem I was having switching my ODBC connection from an v8.0 Postgres database to v8.1.
Below is a list of psqlODBC drivers, versions, dates, and results of my research.
------------------------------------------------------
PostgreSQL Win32Clients 8.00.00.04 1-17-2005 CX=1b8143a9
(OLEDB/ODBC)
------------------------------------------------------
Performance -> Good Performance
Unicode -> Error! Does not Connect to v8.1 UTF8, but ok with 8.0 'Unicode' type
------------------------------------------------------
PostgreSQL 8.00.01.02 8-2-2005 CX=1b103a9
------------------------------------------------------
Performance -> Good Performance
Unicode -> Error! Does not Connect to v8.1 UTF8, but ok with 8.0 'Unicode' type
------------------------------------------------------
PostgreSQL 8.00.01.02 8-2-2005 CX=1b8143a9
------------------------------------------------------
Performance -> Good Performance
Unicode -> Error! Does not Connect to v8.1 UTF8, but ok with 8.0 'Unicode' type
------------------------------------------------------
PostgreSQL (2drivers) 8.01.02.00 1-31-2006 CX=1b8143a9
(bunded with ANSI and UNICODE specific drivers)
------------------------------------------------------
Performance -> Good Performance
Unicode -> Works with UTF8, but requires the selection of the "PostgreSQL Unicode" Driver. This is for both 8.0 and 8.1 versions of Postgres
Hope this helps your ODBC endeavors a bit. The CX is the last part of the connection string specifying parameters for connecting to the database. Declare/Prefetch was selected for the above tests.
One of the Connection String Used for my DSNless connections...
ODBC;DSN=PostgreSQL Unicode;DATABASE=mydatabase;
SERVER=172.10.10.10;
PORT=5432;
A6=;A7=100;A8=4096;B0=254;B1=8190;BI=0;C2=dd_;;CX=1b8143a9
Gary
gwinn7
Recently, I had to research a problem I was having switching my ODBC connection from an v8.0 Postgres database to v8.1.
Below is a list of psqlODBC drivers, versions, dates, and results of my research.
------------------------------------------------------
PostgreSQL Win32Clients 8.00.00.04 1-17-2005 CX=1b8143a9
(OLEDB/ODBC)
------------------------------------------------------
Performance -> Good Performance
Unicode -> Error! Does not Connect to v8.1 UTF8, but ok with 8.0 'Unicode' type
------------------------------------------------------
PostgreSQL 8.00.01.02 8-2-2005 CX=1b103a9
------------------------------------------------------
Performance -> Good Performance
Unicode -> Error! Does not Connect to v8.1 UTF8, but ok with 8.0 'Unicode' type
------------------------------------------------------
PostgreSQL 8.00.01.02 8-2-2005 CX=1b8143a9
------------------------------------------------------
Performance -> Good Performance
Unicode -> Error! Does not Connect to v8.1 UTF8, but ok with 8.0 'Unicode' type
------------------------------------------------------
PostgreSQL (2drivers) 8.01.02.00 1-31-2006 CX=1b8143a9
(bunded with ANSI and UNICODE specific drivers)
------------------------------------------------------
Performance -> Good Performance
Unicode -> Works with UTF8, but requires the selection of the "PostgreSQL Unicode" Driver. This is for both 8.0 and 8.1 versions of Postgres
Hope this helps your ODBC endeavors a bit. The CX is the last part of the connection string specifying parameters for connecting to the database. Declare/Prefetch was selected for the above tests.
One of the Connection String Used for my DSNless connections...
ODBC;DSN=PostgreSQL Unicode;DATABASE=mydatabase;
SERVER=172.10.10.10;
PORT=5432;
A6=;A7=100;A8=4096;B0=254;B1=8190;BI=0;C2=dd_;;CX=1b8143a9
Gary
gwinn7