Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1DEwax85349;
	Tue, 13 Feb 2001 09:58:36 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f1DEwE904462;
	Tue, 13 Feb 2001 09:58:14 -0500 (EST)
To: Dave Page <dpage@vale-housing.co.uk>
cc: "'Hiroshi Inoue'" <Inoue@tpf.co.jp>, Steve Wranovsky <stevew@merge.com>,
	pgsql-interfaces@postgresql.org, pgsql-odbc@postgresql.org
Subject: Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour 
In-reply-to: <8568FC767B4AD311AC33006097BCD3D61A2992@woody.vale-housing.co.uk>
References: <8568FC767B4AD311AC33006097BCD3D61A2992@woody.vale-housing.co.uk>
Comments: In-reply-to Dave Page <dpage@vale-housing.co.uk>
	message dated "Tue, 13 Feb 2001 11:09:53 +0000"
Date: Tue, 13 Feb 2001 09:58:13 -0500
Message-ID: <4459.982076293@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200102/111
X-Sequence-Number: 1068

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