"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> On Tue, Apr 8, 2008 at 1:51 PM, Greg Sabino Mullane <[EMAIL PROTECTED]> wrote:
>> I can state that there would be almost zero chance this would ever be
>> used by DBD::Pg, as it would seem to add overhead with no additional
>> functionality over what we already have. Unless I'm misreading what it
>> does and someone can make the case why I should use it.
> does DBD::pg move arrays in and out of the server? do you parse them
> yourself? if you answer yes to either question you should take a
> second look.
Better support for arrays and composites is certainly something that
people might want, but the problem with this design is that it forces
them to buy into a number of other decisions that they don't necessarily
want.
I could see adding four functions to libpq that create and parse
the textual representations of arrays and records.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
