Re: [PATCHES] libpq type system 0.9a

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Andrew states:
> What about user-defined type registration, sub-classing user or built-in
> type handlers, handling of all data types in binary.  There is a lot
> of new functionality added by this patch to the existing libpq.

All of which may be useful, and may not. Right now DBD::Pg is trying to
move further from libpq, rather than binding closer to it, mainly because
it's a huge dependency burden and it takes forever to add new features.
For example, if this got accepted and put into 8.4, the very earliest DBD::Pg
could take advantage of the code would be mid 2009 (assuming an optimistic
release schedule). Even then, only once 8.4 was widely in use (2010?) would the
average DBD::Pg be compiled against it. And that means lots more forking to handle
the old version until then. But don't take my non-use personally: as you say, this
may be more helpful towards C programmers. I only weighed in because I was asked
to specifically.

> I don't think the appropriate audience got a look at this, maybe posting
> on general or libpq lists.  From my perspective as a long time C coder,
> this made my application code cleaner, easier to maintain and faster in
> many cases.  It removed a lot of code that is now handled by this patch.

Did you even post on -interfaces? I would think that would be the first place
to post, certainly before -patches.

Merlin asks:
> does DBD::pg move arrays in and out of the server? do you parse them
> yourself?  if you answer yes to either question you should take a
> second look.

Yes, we move them into and out of the server, and into and out of Perl arrays
in the process. I'd be happy to give the new way a try however: have you
any sample code and documentation? Emphasis on the latter.

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200804082025
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkf8DcIACgkQvJuQZxSWSshk/QCfS8Ocsoqo6U/LPNhnz9OH9Bm4
83MAoOvsSWkKuyE+LA1UhLpyX0bICQbZ
=2XsW
-----END PGP SIGNATURE-----