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

Re: [INTERFACES] '\' and varchar data type problem w/ MS Access a nd ODBC driver

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] '\' and varchar data type problem w/ MS Access a nd ODBC driver
Date: 1998-08-13 16:08:18
Message-ID: 17576.903024498@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
"Thomas G. Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> One "problem" with the backend is it escapes characters on both input
> _and_ output, which has always struck me as at least partially defeating
> the usefulness of escaping input.

Actually, further experimentation shows that the backend does no such
thing, at least not in tuples returned by SELECT.

psql --- specifically, PQprint() in libpq --- is contributing the
"helpful" doubling of backslashes on printout.  What comes back from
the backend has the number of backslashes it should.

It looks like libpgtcl is contributing some weird backslash response
of its own, which means that things act different but just as broken
if you try to investigate the behavior from Tcl.

Right now I think the backend is behaving properly for SQL command input
and tuple data output.  The bizarreness is in the front ends.

COPY IN/OUT might have some glitches, haven't tried that yet.

			regards, tom lane

pgsql-interfaces by date

Next:From: Tom LaneDate: 1998-08-13 16:41:22
Subject: Re: [INTERFACES] Libpq problems (not)
Previous:From: Dirk ElmendorfDate: 1998-08-13 15:57:39
Subject: Libpq problems

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