From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dave Page <dpage@vale-housing.co.uk>
Cc: 'Hiroshi Inoue' <Inoue@tpf.co.jp>
Cc: Steve Wranovsky <stevew@merge.com>
Cc: pgsql-interfaces@postgresql.org
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour
Date: Tue, 13 Feb 2001 09:58:13 -0500
Message-ID: <4459.982076293@sss.pgh.pa.us> (raw)
In-Reply-To: <8568FC767B4AD311AC33006097BCD3D61A2992@woody.vale-housing.co.uk>
References: <8568FC767B4AD311AC33006097BCD3D61A2992@woody.vale-housing.co.uk>
Dave Page <dpage@vale-housing.co.uk> writes:
> Incidently, pgAdmin gets round the problem by prepending a space to affected
> queries! It seems that postgresql will error with "VACUUM" but not "
> VACUUM". Odd....
Postgres itself doesn't care. However, up till a day or two ago the
ODBC driver would change its behavior depending on leading spaces.
You will probably find that the above-quoted hack no longer works
with the current-CVS ODBC driver ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, dpage@vale-housing.co.uk, Inoue@tpf.co.jp, stevew@merge.com, pgsql-odbc@postgresql.org
Subject: Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour
In-Reply-To: <4459.982076293@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox