Skip site navigation (1)
Skip section navigation (2)
Until version psqlodbc-08_01_0200 the driver could work with Borland (Code
Gear) products like Delphi.
From version psqlodbc-08_02_0100 up to psqlodbc-08_03_0100, when we mark:
* Unknown Sizes = Don't Know;
* Data Type Option = Text as LongVarChar, Unknowns as LongVarChar;
all TEXT fields don't get recognized by the application as MEMO as they did
before.
We are still using the psqlodbc-08_01_0200 version with no problem.
Peripheral Links
Header And Logo
|
Site Navigation
psqlodbc broken since 08_02_0100
- From: "Ricardo David" <dc(dot)ricardo(at)gmail(dot)com>
- To: pgsql-odbc(at)postgresql(dot)org
- Subject: psqlodbc broken since 08_02_0100
- Date: Thu, 6 Mar 2008 07:38:24 -0300
- Message-id: <9bcc33ca0803060238w2d38b837kbc4e3390b424a2ef(at)mail(dot)gmail(dot)com>
Until version psqlodbc-08_01_0200 the driver could work with Borland (Code
Gear) products like Delphi.
From version psqlodbc-08_02_0100 up to psqlodbc-08_03_0100, when we mark:
* Unknown Sizes = Don't Know;
* Data Type Option = Text as LongVarChar, Unknowns as LongVarChar;
all TEXT fields don't get recognized by the application as MEMO as they did
before.
We are still using the psqlodbc-08_01_0200 version with no problem.
- Follow-Ups:
- Re: psqlodbc broken since 08_02_0100
- From: Hiroshi Inoue
- Re: psqlodbc broken since 08_02_0100
- Prev by Date: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
- Next by Date: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
- Previous by thread: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
- Next by thread: Re: psqlodbc broken since 08_02_0100
- Indexes: