t == [EMAIL PROTECTED] writes:
t> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
t> > t == [EMAIL PROTECTED] 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
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> t == [EMAIL PROTECTED] writes:
> t> Uh, no, that is certainly *not* the behavior you were getting in 8.1;
> t> 8.1's behavior corresponds to both switches off.
> OK. I'm confused. With 8.1.5 we never had to do anything special
> with backslashes.
t == [EMAIL PROTECTED] writes:
t> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
t> > t == [EMAIL PROTECTED] writes:
t> > t> Well, if your intent is to replicate 8.1's behavior, you should
instead
t> > t> frob the other switch.
t> > I now have
t> > escape_string_warning = off
t> > and
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> t == [EMAIL PROTECTED] writes:
> t> Well, if your intent is to replicate 8.1's behavior, you should instead
> t> frob the other switch.
> I now have
> escape_string_warning = off
> and
> standard_conforming_strings = on
> in postgresql.conf and
t == [EMAIL PROTECTED] writes:
t> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
t> > t == [EMAIL PROTECTED] writes:
t> > t> See standard_conforming_strings and escape_string_warning.
t> > Excellent. I had missed the standard_conforming_strings and will turn
t> > this on. Hold on. Yes, th
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> t == [EMAIL PROTECTED] writes:
> t> See standard_conforming_strings and escape_string_warning.
> Excellent. I had missed the standard_conforming_strings and will turn
> this on. Hold on. Yes, that did it. Thanks so much.
Well, if your intent is
t == [EMAIL PROTECTED] writes:
t> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
t> > I just upgraded to 8.3.3 from 8.1.5 and noticed that backslashes are
t> > handled completely differently now. For example,
t> See standard_conforming_strings and escape_string_warning.
Excellent. I had mi
b == [EMAIL PROTECTED] writes:
b> I just upgraded to 8.3.3 from 8.1.5 and noticed that backslashes are
b> handled completely differently now. For example,
It looks like the default for escape_string_warning is now "on".
However, it says in the docs that future versions will treat the
backslas
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> I just upgraded to 8.3.3 from 8.1.5 and noticed that backslashes are
> handled completely differently now. For example,
See standard_conforming_strings and escape_string_warning.
regards, tom lane
--
Sent via pgsql-general
I just upgraded to 8.3.3 from 8.1.5 and noticed that backslashes are
handled completely differently now. For example,
db=# insert into junk (cifs) values ('\\f\bar');
WARNING: nonstandard use of \\ in a string literal
LINE 1: insert into junk (cifs) values ('\\f\bar');
10 matches
Mail list logo
