[EMAIL PROTECTED] wrote:
> > I expect you intend to get at least the hooks in, right?
[...]
libpqtypes was designed to handle this with our without hooking. (the
'hooking' debate was mainly about exactly how libpq and libpqtypes was
going to be separated).
libpqtypes had a superclassing concept (not much discussed on the
lists) where you could introduce new type handlers that wrapped
existing ones and was desgined exactly for things like this.
That sounds cool. So in a way you do have the hooks.
A patch has been submited for supporting libpq object hooks, which allows one to
associate private storage with a PGconn or PGresult object. The hook is called
when a conn or result is created or destroyed (PQreset for conn as well).
http://archives.postgresql.org/pgsql-patches/2008-04/msg00309.php
For libpqtypes, this means it can operate outside of libpq. libpqtypes was
initially designed as a direct extension to libpq (internal code), but the
community prefered using a generic hook interface that allowed libpqtypes to
work externally.
--
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
