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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
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 16:33:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Dave Page <dpage(at)vale-housing(dot)co(dot)uk> writes:
> 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 :-)

Okay.  Now that I look at it, the change I was thinking of wouldn't have
affected the behavior for utility statements anyway.  What was broken
was statement_type() in statement.c --- it would fail to recognize any
statement with leading spaces, and would always return STMT_TYPE_OTHER.
But that is the right answer for VACUUM and suchlike.  The case it
really crashed and burned on was SELECT with leading spaces...

			regards, tom lane

In response to

pgsql-odbc by date

Next:From: Cedar CoxDate: 2001-02-13 21:17:24
Subject: RE: Re: RE: [PATCHES] Re: [HACKERS] 6.2 protocol
Previous:From: Dave PageDate: 2001-02-13 16:15:43
Subject: RE: RE: [INTERFACES] 7.1 beta 3 Linux ODBC BEGINBehaviour

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