From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: andrew5@ece.cmu.edu, PostgreSQL-patches <pgsql-patches@postgresql.org>
Subject: Re: [BUGS] BUG #2171: Differences compiling plpgsql in
Date: Thu, 02 Feb 2006 16:41:01 -0500
Message-ID: <19109.1138916461@sss.pgh.pa.us> (raw)
In-Reply-To: <1138905401.5342.15.camel@swithin>
References: <200602020448.k124mjG25834@candle.pha.pa.us>
<1138905401.5342.15.camel@swithin>
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?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, pgman@candle.pha.pa.us, pgsql-patches@postgresql.org
Subject: Re: [BUGS] BUG #2171: Differences compiling plpgsql in
In-Reply-To: <19109.1138916461@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox