Re: backslashes in 8.3.3

From: "Brandon Metcalf" <bmetcalf(at)nortel(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: backslashes in 8.3.3
Date: 2008-06-24 18:37:01
Message-ID: Pine.LNX.4.58L.0806241335170.9186@cash.us.nortel.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

t == tgl(at)sss(dot)pgh(dot)pa(dot)us writes:

t> "Brandon Metcalf" <bmetcalf(at)nortel(dot)com> writes:
t> > t == tgl(at)sss(dot)pgh(dot)pa(dot)us writes:
t> > t> Uh, no, that is certainly *not* the behavior you were getting in 8.1;
t> > t> 8.1's behavior corresponds to both switches off.

t> > OK. I'm confused. With 8.1.5 we never had to do anything special
t> > with backslashes. When we upgraded to 8.3.3, backslashes in our
t> > INSERTs caused problems until we turn _on_
t> > standard_conforming_strings.

t> Maybe something changed on the client side? 8.1 definitely does not have
t> standard_conforming_strings, but perhaps you had some client-side
t> code that compensated by inserting backslashes.

No, nothing changed on the client side. I know you know what you're
talking about, though. At any rate, I've got the behavior I need now.

--
Brandon

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2008-06-24 20:56:01 Re: Probably been asked a hundred times before.
Previous Message Kevin Hunter 2008-06-24 18:30:54 Re: Probably been asked a hundred times before.