Re: [BUGS] BUG #2171: Differences compiling plpgsql in - Mailing list pgsql-patches

From Andrew Dunstan
Subject Re: [BUGS] BUG #2171: Differences compiling plpgsql in
Date
Msg-id 1138916707.5342.41.camel@swithin
Whole thread Raw
In response to Re: [BUGS] BUG #2171: Differences compiling plpgsql in  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Thu, 2006-02-02 at 16:41 -0500, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
> > As a matter of curiosity, why does ecpg handle dollar quoting like that?
> > psql, for example, happily just passes a dollar quoted string through to
> > the backend, without any need to convert it to a conventionally quoted
> > string.
>
> Doesn't ecpg have to convert string literals into C string constants?
>


I believe so. But doesn't it do that by surrounding them with double
quotes, and escaping embedded double quotes (and now newlines) ? The
backend still needs to see what it will accept as a quote delimiter,
surely.

cheers

andrew


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #2171: Differences compiling plpgsql in
Next
From: Stephen Frost
Date:
Subject: Re: pg_restore COPY error handling