-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Another point is that since the ODBC driver is C anyway, there are no > cross-language issues for it in relying on libpq. This is quite > different IMHO from the situation for JDBC, or DBD::Pg, where there are > advantages in having a single-language solution. This is not so much of an issue with DBD::Pg - it already uses quite a bit of C code[1]. not only from libpq, but because DBI is written in C, and because it is handy sometimes to use non-libpq pgsql code, such as some of the quoting stuff. Having libpq is definitely a bonus for us (DBD::Pg), and we've never really had an issue with libpq until now, and it's getting fixed, so no worries. [1] Well, C and pseudo-C XS code anyway. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200409202318 -----BEGIN PGP SIGNATURE----- iD8DBQFBT52RvJuQZxSWSsgRAvWXAJ9FTLnVzFULYKEF1Z16EnNJw6BxewCdFHW5 13hbl5M6pT9+oezDpAVetIM= =Dpjb -----END PGP SIGNATURE-----
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly