From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
Cc: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] libpq type system 0.9a |
Date: | 2008-04-08 18:38:39 |
Message-ID: | 5592.1207679919@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
> On Tue, Apr 8, 2008 at 1:51 PM, Greg Sabino Mullane <greg(at)turnstep(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-04-08 18:42:09 | Re: [PATCHES] libpq type system 0.9a |
Previous Message | Andrew Chernow | 2008-04-08 18:34:51 | Re: [PATCHES] libpq type system 0.9a |
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-04-08 18:42:09 | Re: [PATCHES] libpq type system 0.9a |
Previous Message | Andrew Chernow | 2008-04-08 18:34:51 | Re: [PATCHES] libpq type system 0.9a |