From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "F Harvell" <fharvell(at)fts(dot)net> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Andrew Pimlott" <pimlott(at)idiomtech(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: non-standard escapes in string literals |
Date: | 2002-05-08 16:47:46 |
Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA4961DC7@m0114.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > This also poses the biggest problem in terms of legacy compatibility.
> > Perhaps the answer is to add a runtime config option (and default it
> > to ANSI) and possibly deprecate the C escaping.
>
> While I wouldn't necessarily object to a runtime option, I do object
> to both the other parts of your proposal ;-). Backslash escaping is
> not broken; we aren't going to remove it or deprecate it, and I would
> vote against making it non-default.
When we are talking about the places where you need double escaping
(once for parser, once for input function) to make it work, I would also
say that that is very cumbersome (not broken, since it is thus documented) :-)
I would also default to strict ANSI, but not depricate the escaping when set.
All imho of course.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-05-08 17:00:07 | Bad side-effect from making EXPLAIN return a select result |
Previous Message | Marc G. Fournier | 2002-05-08 16:41:18 | Re: Path to PostgreSQL portabiliy |