Re: [BUGS] BUG #2171: Differences compiling plpgsql in

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, andrew5(at)ece(dot)cmu(dot)edu, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #2171: Differences compiling plpgsql in
Date: 2006-02-02 21:45:06
Message-ID: 1138916707.5342.41.camel@swithin
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-interfaces pgsql-patches

On Thu, 2006-02-02 at 16:41 -0500, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephan Szabo 2006-02-02 23:08:45 Re: BUG #2231: Incorrect Order By
Previous Message Tom Lane 2006-02-02 21:41:01 Re: [BUGS] BUG #2171: Differences compiling plpgsql in

Browse pgsql-interfaces by date

  From Date Subject
Next Message Bruce Momjian 2006-02-03 03:55:23 Re: [BUGS] BUG #2171: Differences compiling plpgsql in ecpg
Previous Message Tom Lane 2006-02-02 21:41:01 Re: [BUGS] BUG #2171: Differences compiling plpgsql in

Browse pgsql-patches by date

  From Date Subject
Next Message Josh Berkus 2006-02-02 22:13:24 Re: Multiple logical databases
Previous Message Tom Lane 2006-02-02 21:41:01 Re: [BUGS] BUG #2171: Differences compiling plpgsql in