Re: cvs postgresql current lacks 'ksqo' ? odbc/pgadmin

Tino Wildenhain wrote:
> Hi Tom, Bruce,
>
> --On Mittwoch, 14. August 2002 14:09 -0400 Bruce Momjian
> <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
>
> >
> > I didn't realize ODBC would error out if a SET came that wasn't
> > recognized. Can you confirm this? We can add it to 7.3 backend as an
> > invisible option (not in postgresql.conf) and mention in the TODO it
> > should be removed in 7.4 or 7.5.
>
> I can confirm this. Using odbc connection it trows the error as expected.
> If I remove the setting [ ] disable ksqo in the odbc driver options,
> everything works well. (This is unfortunately impossible for PgAccess,
> since it does not use an ODBC DSN)
>
> Perhaps its a better idea to update the odbc driver for 7.3.

Well, the 7.3 driver and the current driver at odbc.postgresql.org
should handle this correctly already and not enable ksqo.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073