Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.8.8/8.7.5) with ESMTP id MAA25843 for ; Thu, 13 Aug 1998 12:09:33 -0400 (EDT) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id MAA17578; Thu, 13 Aug 1998 12:08:18 -0400 (EDT) To: "Thomas G. Lockhart" cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] '\' and varchar data type problem w/ MS Access a nd ODBC driver In-reply-to: Your message of Thu, 13 Aug 1998 02:38:04 +0000 <35D2518C.EBF8ECFD@alumni.caltech.edu> Date: Thu, 13 Aug 1998 12:08:18 -0400 Message-ID: <17576.903024498@sss.pgh.pa.us> From: Tom Lane "Thomas G. Lockhart" 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