| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Gregory Stark <stark(at)enterprisedb(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] libpq type system 0.9a |
| Date: | 2008-04-09 13:17:16 |
| Message-ID: | 47FCC1DC.3020202@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Chernow wrote:
>
> Yeah, currently composites and arrays only support binary results in
> libpqtypes. This forces any array elementType or any member of a
> composite to have a send/recv routine. Using the "fallback to text
> output" approach, this limitation on array elements and composite
> members would be removed.
>
Actually, I am confusing the way the protocol handles arrays and
composites (as a single column value, vs. the way libpqtypes handles
these (as a separate result object). for instance, the members of a
composite inherit the format of the column within the protocol. To
allow one member of a composite to be text formatted and another be
binary, would require a change to the protocol, an additional format
value per member header.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2008-04-09 13:26:10 | Re: [PATCHES] libpq type system 0.9a |
| Previous Message | Michael Meskes | 2008-04-09 13:09:58 | Re: [PATCHES] libpq type system 0.9a |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2008-04-09 13:26:10 | Re: [PATCHES] libpq type system 0.9a |
| Previous Message | Michael Meskes | 2008-04-09 13:09:58 | Re: [PATCHES] libpq type system 0.9a |