Tom Lane wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> > On Tue, May 10, 2011 at 06:20:23PM +0200, Martin Pitt wrote:
> >> Since HISTORY does not mention this, is that an explicit decision to
> >> finally deprecate the old \' syntax (which would be great, as it makes
> >> this thing a lot more robust and deterministic, but it might be worth
> >> mentioning it in HISTORY), or an unintended side effect?
> > release notes clearly mentions is:
> > http://developer.postgresql.org/pgdocs/postgres/release-9-1.html
> > - Change the default value of standard_conforming_strings to on (Robert Haas)
> > This removes a long-standing incompatibility with the SQL standard;
> > escape_string_warning has produced warnings about this usage for years. E''
> > strings are the proper way to embed escapes in strings and are unaffected by
> > this change.
> Hmm ... considering that's the first thing in the release notes, I'm
> surprised Martin missed it. Maybe he was looking for something
> mentioning backslashes ... should we add a bit that specifically says
> that backslashes are now no-ops by default?
I added the word "backslash" before escapes in the attached applied
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ It's impossible for everything to be true. +
Description: text/x-diff (909 bytes)
In response to
pgsql-bugs by date
|Next:||From: 李兵||Date: 2011-05-11 03:09:08|
|Subject: Re: BUG #5994: Can't excute DBI->connect to oracle by client site|
|Previous:||From: Bruce Momjian||Date: 2011-05-10 23:44:35|
|Subject: Re: Re: [BUGS] BUG #5957: createdb with description
and md5 auth forces to provide password twice|