-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> Using DBI/DBD::Pg would raise another issue - what version of libpq
> would it be using? Not the one in the build being tested, that's for
> sure.
Er...why not? That's what psql uses. As for those advocating using a
custom C program written using libpq - that's basically what
DBI/DBD::Pg ends up being! Only with a shiny Perl outside and years
of real-world testing and usage.
> If you really want to use Perl then either a Pure Perl DBI driver
> (which Greg has talked about) or a thin veneer over libpq such as we
> used to have in contrib seems a safer way to go.
I'm still *very* interested in making a libpq-less pure perl driver,
if anyone feels like funding it, let me know! :)
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 201001071236
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAktGHF0ACgkQvJuQZxSWSsiFmACfUJbRDUJGvDTJNjgj/dyQKVCA
tZwAn2fiXKNWbWzYXobrHZjeE8aSSiVv
=sGzK
-----END PGP SIGNATURE-----
