Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
- From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
- To: Jack Wilson <ljwilson(at)digitalav(dot)com>
- Cc: pgsql-odbc(at)postgresql(dot)org
- Subject: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
- Date: Sat, 08 Mar 2008 03:09:12 +0900
- Message-id: <47D184C8(dot)1010101(at)tpf(dot)co(dot)jp>
Jack Wilson wrote:
Hiroshi, No problem. I understand perfectly.
I can't test my change with 8.3 servers by myself now. Could you try the driver testing for 8.3.0101 at http://www.geocities.jp/inocchichichi/psqlodbc/index.html ? regards, Hiroshi Inoue
- Follow-Ups:
- References:
- Prev by Date: Cannot get psqlODBC to work
- Next by Date: Re: psqlodbc broken since 08_02_0100
- Previous by thread: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
- Next by thread: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
- Indexes: