Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons - Mailing list pgsql-odbc

From Jack Wilson
Subject Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons
Date
Msg-id OF337F385E.6CCE40CA-ON85257404.00484939-85257404.0048B574@digitalav.com
Whole thread Raw
In response to Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons  (Hiroshi Inoue <inoue@tpf.co.jp>)
Responses Re: " for read only" clause appended for safety when UseDeclareFetch=1 breaks some sql statements with trailing semicolons  (Hiroshi Inoue <inoue@tpf.co.jp>)
List pgsql-odbc

Hiroshi,

No problem. I understand perfectly.

Thanks for looking at it!

...jack

--
********************************************
Who:    L Jack Wilson
Where:  ljwilson@dNiOgSiPtAaMlav.com
How:    Remove Capital Letters from above for a valid email address
Why:    Standard Disclaimer fits nicely here.

pgsql-odbc by date:

Previous
From: "Ricardo David"
Date:
Subject: psqlodbc broken since 08_02_0100
Next
From: Glyn Astill
Date:
Subject: Cannot get psqlODBC to work