| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jonathan Guthrie <jguthrie(at)brokersys(dot)com> |
| Subject: | Re: BUG #4027: backslash escaping not disabled in plpgsql |
| Date: | 2008-03-12 13:18:41 |
| Message-ID: | 200803121318.m2CDIfj22909@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Peter Eisentraut wrote:
> Tom Lane wrote:
> > plpgsql does not consider standard_conforming_strings --- it still uses
> > backslash escaping in its function bodies regardless. Since the
> > language itself is not standardized, I see no particular reason that
> > standard_conforming_strings should govern it.
>
> I think plpgsql should behave either consistently with the rest of PostgreSQL
> or with Oracle, which it is copied from.
Agreed. standard_conforming_strings should affect _all_ strings.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurent Birtz | 2008-03-12 14:02:34 | Re: LISTEN/NOTIFY race condition? |
| Previous Message | Bruce Momjian | 2008-03-12 13:11:48 | Re: BUG #3681: fillers are NULL in pgbench |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-03-12 13:20:47 | Re: [ADMIN] 8.2.4 patches? (fwd) |
| Previous Message | Meetesh Karia | 2008-03-12 12:25:14 | Encoding problems with migration from 8.0.14 to 8.3.0 on Windows |