Bob Woodside wrote:
> Here's a curious problem. We recently exported an Access table to
> PostgreSQL. The table has 3 column names containing apostrophes (or
> single-quotes, if you like). This seems to confuse some bit of parsing
> logic somewhere in the ODBC path, whenever a dynaset query is sent from
> Access that has an odd number of references to these apostrophic names.
> If we issue a query with an odd number of these references, the
> end receives something like this:
> > 'SELECT "ID","Month called or rec'd form","FullName" FROM
> > WHERE "ID" = ? OR "ID" = ? OR "ID" = ? OR "ID" = ? OR "ID" = ? OR "ID"
> > OR "ID" = ? OR "ID" = ? OR "ID" = ? OR "ID" = ?'
Psqlodbc driver has been unaware of double-quotes(") .
Probably it's the cause.
Recently I changed the driver to check double-quotes.
Could you try the CVS snapshot ?
> which, of course, it rejects.
> If we issue a query with an even number of such references, the
> end receives something like this, and is very happy:
> > SELECT "ID","Month called or rec'd form","Day called or rec'd
> > FROM "GHI-practice2" WHERE "ID" = 1 OR "ID" = 3 OR "ID" = 4 OR "ID" =
> > OR "ID" = 8 OR "ID" = 9 OR "ID" = 11 OR "ID" = 12 OR "ID" = 13 OR "ID"
> I've captured traces from the ODBC manager and from the pgsql
> and can forward them if you like. I haven't yet had time to try to dig
> into this any deeper to determine whether the bug is in the Postgres
> driver or in MS code.
> Has anyone got any idea where the problem lies? Is it a known
> with a known workaround, or a new, um, opportunity?
pgsql-odbc by date
|Next:||From: Hiroshi Inoue||Date: 2001-06-16 01:06:01|
|Subject: Re: SQLConnect Core dump with Purify|
|Previous:||From: Johann Zuschlag||Date: 2001-06-15 17:47:13|
|Subject: Re: slow performance postgres 7.0.3 and odbc|