| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Jeff Davis <jdavis-pgsql(at)empires(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Marko Kreen <marko(at)l-t(dot)ee>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Subject: | Re: #escape_string_warning = off |
| Date: | 2005-08-03 13:01:07 |
| Message-ID: | 200508031501.08338.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Mittwoch, 3. August 2005 01:18 schrieb Jeff Davis:
> I guess what I'm trying to find out: does this mean that after all this
> change to the way strings are handled in the future, PostgreSQL still
> won't be standards-compliant for the basic '' string?
It will be more conforming regarding backslashes. There may be other
conformance issues, but they are not considered here.
> Also, let's say I have apps now in 7.4/8.0, and I want them to be
> forward-compatible. Should I make a type called E so that the E''
> notation will work, and then use that for strings? What is the "right"
> way to do it?
To be standards-conforming, don't use any backslash escapes. If you must use
them, use the E'' notation.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-08-03 13:40:24 | Re: #escape_string_warning = off |
| Previous Message | Peter Eisentraut | 2005-08-03 12:23:33 | CVS repository for translations |