Skip site navigation (1) Skip section navigation (2)

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

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, pgsql-odbc(at)postgresql(dot)org
Subject: RE: RE: [INTERFACES] 7.1 beta 3 Linux ODBC BEGINBehaviour
Date: 2001-02-13 15:19:40
Message-ID: 8568FC767B4AD311AC33006097BCD3D61A2994@woody.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc

> -----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...

Regards,

Dave.

pgsql-odbc by date

Next:From: Dave PageDate: 2001-02-13 16:15:43
Subject: RE: RE: [INTERFACES] 7.1 beta 3 Linux ODBC BEGINBehaviour
Previous:From: Tom LaneDate: 2001-02-13 14:58:13
Subject: Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group