This patch has an identity crisis. We initially called it PGparam (possibly
mispelled several times as PQparam) and then changed it to libpq type system
(typesys).
Several on patches started to call it libpqtypes, even I did. Any objections to
fixing the name to libpqtypes?
Any thoughts on the hooking suggested by Tom? It sounds like it should be
generic enough so more than just libpqtypes can make use of it. I think
something of this nature should have input before I do anything.
Possible Hook points: (at least ones needed by libpqtypes)
conn_create
conn_reset
conn_destroy
result_create
result_destroy
I guess libpqtypes would have to maintain a map of conns and results? Right now
it can associate type info because we added members to conn and result. When
conn_create(conn) is called, libpqtypes would need to map this by pointer
address (as it is all it has as an identifier). Still feels like maybe there
should be a void* in a conn and result used for per-connection/result based info
(libpqtypes or not).
--
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
