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/
