Re: Correctly producing array literals for prepared statements

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Kenneth Marshall <ktm(at)rice(dot)edu>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Correctly producing array literals for prepared statements
Date: 2011-02-23 19:21:08
Message-ID: 4D655E24.7000809@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Binary mode had serious limitations, such as portability.
>

What are the other limitations?

As far as portability is concerned, we are using it on many different
operating systems and architectures without issue. Even our most recent
bump to 9.0.1 and 9.0.3 was flawless in regard to libpq/libpqtypes.

> We do need some support in libpq for constructing and deconstructing
> arrays (and probably for composites too, although that will be harder, I
> suspect).
>

[sigh...]

--
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-02-23 19:48:22 Re: How to extract a value from a record using attnum or attname?
Previous Message Kevin Grittner 2011-02-23 19:20:16 Re: How to extract a value from a record using attnum or attname?