From: "Sabin Coanda" <sabin.coanda@deuromedia.ro>
Subject: Re: plpgsql language not aware of standard_conforming_strings ?
Date: Mon, 12 Nov 2007 13:10:50 +0200
Organization: Hub.Org Networking Services
Lines: 36
Message-ID: <fh9cbj$2pd2$1@news.hub.org>
References: <fh99cq$2cfn$1@news.hub.org>
To: pgsql-sql@postgresql.org


"Sabin Coanda" <sabin.coanda@deuromedia.ro> wrote in message 
news:fh99cq$2cfn$1@news.hub.org...
...
>
> How can I get my desired function that means when I call test( 'a\b' ) it 
> will return 'a\\b' ?
>

The problem seems to be the constant evaluation in plpgsql functions which 
is not aware of  standard_conforming_strings.
An answer may be to build my own replace function, that doesn't use constant 
evaluation inside.
For instance:

CREATE OR REPLACE FUNCTION myreplace(sText varchar, sSrc varchar, sDst 
varchar)  RETURNS varchar AS $BODY$
BEGIN
 RETURN replace( sText, sSrc, sDst );
END;
$BODY$
  LANGUAGE 'plpgsql' VOLATILE;


Using this function will give the expected result, when 
standard_conforming_strings = 'on', so
SELECT myreplace( 'a\b', '\', '\\' ); will give the result 'a\\b' as 
expected.

In fact this is an workaround :((. It would be nice to make the language to 
works like that :).

Regards,
Sabin