"Donald Fraser" <postgres(at)kiwi-fraser(dot)net> writes:
> According to the release notes, PostgreSQL still handles escape =
> characters in strings as it has in the past, yet PL/pgSQL functions that =
> use escape characters within the string definition for RAISE EXCEPTION =
> are ignored, unless the function is created using the old style quote =
> definition (not $$).
I think you are confused. plpgsql has never interpreted \n as a return;
if that's happening, it's in the string literal parser that eats the
function body string.
Looking at the source code, it appears that plpgsql's scanner treats
E'' and '' strings the same, which we probably should change sometime
(though the risks for breaking existing functions, perhaps with
unpleasant security implications, seem high). But the examples you
give address what happens when the string is read by CREATE FUNCTION,
not what plpgsql does when running the function.
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Geoff Taylor||Date: 2007-06-26 21:33:27|
|Subject: BUG #3414: client-only install fails due to parse.h file not found|
|Previous:||From: Donald Fraser||Date: 2007-06-26 17:56:41|
|Subject: PL/pgSQL RAISE EXCEPTION ignores escape characters even with new E'' string syntax|