From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] '\' and varchar data type problem w/ MS Access a nd ODBC driver
Date: Thu, 13 Aug 1998 12:08:18 -0400
Message-ID: <17576.903024498@sss.pgh.pa.us> (raw)
In-Reply-To: <35D2518C.EBF8ECFD@alumni.caltech.edu>
"Thomas G. Lockhart" <lockhart@alumni.caltech.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, lockhart@alumni.caltech.edu
Subject: Re: [INTERFACES] '\' and varchar data type problem w/ MS Access a nd ODBC driver
In-Reply-To: <17576.903024498@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox