Tom Lane wrote:
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.
regards, tom lane
What decisions are we forcing upon the libpq user?
Well, most of the functionality is handled by about 3 functions (putf,
getf, and paramexec). The difference is, our patch is not limited to
only handling text arrays and composites. It can do it all, which we
thought would of been a requirement to get approved.
There is a performance boost to handling arrays and composites in
binary, which we use a lot because there are no stored procedures (note,
not trying to take a jab about stored procedures, just giving an example
of how we use and abuse arrays and composites).
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
