Re: Correctly producing array literals for prepared statements - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Correctly producing array literals for prepared statements
Date
Msg-id AANLkTi=CyXRYC54mA-3atQ22UMc1_1e92A0tWVi1qTjy@mail.gmail.com
Whole thread Raw
In response to Correctly producing array literals for prepared statements  (Peter Geoghegan <peter.geoghegan86@gmail.com>)
Responses Re: Correctly producing array literals for prepared statements
Re: Correctly producing array literals for prepared statements
List pgsql-hackers
On Wed, Feb 23, 2011 at 4:16 AM, Peter Geoghegan
<peter.geoghegan86@gmail.com> wrote:
> Since Postgres only supports encodings that are ASCII supersets, I
> don't believe that I have to consider encoding - only my clients do.
>

This is only true for server encodings. In a client library I think
you lose on this and do have to deal with it. I'm not sure what client
encodings we do support that aren't ascii-supersets though, it's
possible none of them generate quote characters this way.

I'm a bit surprised libpqxx isn't using binary mode internally though.
This would at least avoid the problems with encoding. However I'm not
sure things like the array binary format are really stable and
portable enough to really use from a client library. Some datatypes
might be dependent on the server ABI (floats -- I'm looking at you) so
that might make it difficult or impossible.

-- 
greg


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Correctly producing array literals for prepared statements
Next
From: "Kevin Grittner"
Date:
Subject: Re: SSI bug?