RE: RE: [INTERFACES] 7.1 beta 3 Linux ODBC BEGINBehaviour

> -----Original Message-----
> From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
> Sent: 13 February 2001 15:20
> To: 'Tom Lane'
> Cc: 'Hiroshi Inoue'; pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] RE: [INTERFACES] 7.1 beta 3 Linux ODBC
> BEGINBehaviour
>
>
>
>
> > -----Original Message-----
> > From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> > Sent: 13 February 2001 14:58
> > To: Dave Page
> > Cc: 'Hiroshi Inoue'; Steve Wranovsky;
> pgsql-interfaces(at)postgresql(dot)org;
> > pgsql-odbc(at)postgresql(dot)org
> > Subject: Re: [ODBC] RE: [INTERFACES] 7.1 beta 3 Linux ODBC
> > BEGINBehaviour
> >
> >
> > Dave Page <dpage(at)vale-housing(dot)co(dot)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 ...
> >
>
> Awwww nuts! If that's the case pgAdmin has just broken in
> numerous places
> :-(. I'll have to test it...

Just recompiled the driver and it still works :-)

Regards, Dave.