| 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>, Steve Wranovsky <stevew(at)merge(dot)com>, pgsql-interfaces(at)postgresql(dot)org, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour |
| Date: | 2001-02-13 14:58:13 |
| Message-ID: | 4459.982076293@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces pgsql-odbc |
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 ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gupta, Preeti (P.) | 2001-02-14 10:35:18 | Urgent Query |
| Previous Message | Dave Page | 2001-02-13 11:09:53 | RE: [ODBC] RE: 7.1 beta 3 Linux ODBC BEGINBehaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2001-02-13 15:19:40 | RE: RE: [INTERFACES] 7.1 beta 3 Linux ODBC BEGINBehaviour |
| Previous Message | Constantin S. Svintsoff | 2001-02-13 12:00:19 | BEGIN Behaviour |