From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Andrew Chernow" <ac(at)esilo(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: PQParam version 0.5 |
Date: | 2007-12-06 19:12:22 |
Message-ID: | b42b73150712061112y51df6c8v4f4920f58fb2e9ad@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Dec 6, 2007 11:58 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I want to buy into the idea that libpq should know explicitly about each
> and every backend datatype.
I don' t necessarily agree with this. First of all, the server gives
you an oid for the column which introduces the dependency...this has
been the case for a while now. Secondly, why shouldn't the client
library understand the data the server hands out, at least for
built-in types.
Usings arrays in client side apps is a huge pain...and not efficient
for large arrays. Same for the variable length geometry types.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-12-06 19:34:42 | Re: Better default_statistics_target |
Previous Message | Andrew Chernow | 2007-12-06 18:41:38 | Re: PQParam version 0.5 |