| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Jonathan Guthrie" <jguthrie(at)brokersys(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql |
| Date: | 2009-04-10 18:57:10 |
| Message-ID: | 28556.1239389830@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> The aspect of 8.3 behavior that concerns me most is that neither the
> author of a function, nor anyone using it, can control or predict
> which way a string literal with a backslash will be interpreted,
> unless the author explicitly specifies the SET
> standard_conforming_strings clause in the function declaration.
Yeah. This is one reason why I'm still afraid to flip the default
value of standard_conforming_strings --- there seems too much risk
of widespread breakage.
I don't have a good solution for it, but I agree it's a problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2009-04-10 19:11:22 | Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql |
| Previous Message | Tom Lane | 2009-04-10 18:47:32 | Re: possible bug not in open items |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-04-10 19:01:05 | Re: A renewed plea for inclusion of zone.tab |
| Previous Message | Kevin Grittner | 2009-04-10 18:40:06 | Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql |