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
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
Peter Eisentraut [EMAIL PROTECTED] writes:
Tom Lane wrote:
I believe the reason for
not changing it was that it seemed too likely to break existing
functions, with potentially nasty consequences if they chanced to be
security definers.
Is this actually true or did we just forget it? :-)
I
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
Peter Eisentraut wrote:
Bruce Momjian wrote:
Agreed. standard_conforming_strings should affect _all_ strings.
We might need another transition period over a few releases with a
separate plpgsql_standard_conforming_strings parameter. Just changing it
immediately is perhaps a bit risky.
Bruce Momjian wrote:
Agreed. standard_conforming_strings should affect _all_ strings.
We might need another transition period over a few releases with a
separate plpgsql_standard_conforming_strings parameter. Just changing it
immediately is perhaps a bit risky.
--
Sent via pgsql-bugs
The following bug has been logged online:
Bug reference: 4027
Logged by: Jonathan Guthrie
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Debian Gnu/Linux unstable 2.6.24
Description:backslash escaping not disabled in plpgsql
Details:
I
Jonathan Guthrie [EMAIL PROTECTED] writes:
I have set the standard_conforming_strings to on in my settings ...
However, when I attempt to define this function:
create function foo (out r refcursor) as $bar$
begin
open r for
select * from user_data
where name_first like name escape
