Skip site navigation (1)
Skip section navigation (2)
Hiroshi,
No problem. I understand perfectly.
Thanks for looking at it!
...jack
--
********************************************
Who: L Jack Wilson
Where: ljwilson(at)dNiOgSiPtAaMlav(dot)com
How: Remove Capital Letters from above for a valid email address
Why: Standard Disclaimer fits nicely here.
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: Jack Wilson <ljwilson(at)digitalav(dot)com>
- To: inoue(at)tpf(dot)co(dot)jp
- Cc: pgsql-odbc(at)postgresql(dot)org, pgsql-odbc-owner(at)postgresql(dot)org
- Subject: Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
- Date: Thu, 6 Mar 2008 08:14:00 -0500
- Message-id: <OF337F385E(dot)6CCE40CA-ON85257404(dot)00484939-85257404(dot)0048B574(at)digitalav(dot)com>
Hiroshi,
No problem. I understand perfectly.
Thanks for looking at it!
...jack
--
********************************************
Who: L Jack Wilson
Where: ljwilson(at)dNiOgSiPtAaMlav(dot)com
How: Remove Capital Letters from above for a valid email address
Why: Standard Disclaimer fits nicely here.
- Follow-Ups:
- References:
- Prev by Date: psqlodbc broken since 08_02_0100
- Next by Date: Cannot get psqlODBC to work
- 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: