-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
For those who may not have noticed, I released a 2.1.0 earlier tonight, mostly just fixing some bugs found in 2.0.0 and adding in some threaded Perl support. > Cool! (trace flags) Yeah, these are pretty neat, I'm glad I finally got around to doing this. If anyone has other ideas of ways to trace, please let me know. Right now, I've got SQL, LIBPQ, and START as the major ones, which do pretty much what you might imagine they do. There's plenty of room for more flags though, and the cost to implement them is very low. As a bonus, I think the code is a lot easier to read now too. > +DBD::Pg only supports one flag, B<SQL>, that is defined with > +DBI itself. Flags can be combined by using the param_trace_flags >... > And list a bunch of others. How can both statements be true? Sorry, that was poorly written. I was trying to say that we support the only DBI flag, in addition to our own flags. As far as I know, we're the first to use the SQL flag (or any flags, really). I did a quick rewrite of the section. Thanks for the proofing! > +http://search.cpan.org/~dbdpg/ > Looks like you've been uploading the releases using your own CPAN ID, > rathe than dbdpg. So you should probably change that URL to > > http://search.cpan.org/dist/DBD-Pg/ > > Because the above URL only has 1.49 listed. Crap. Darn cookies, I don't really pay attention anymore to who I'm logged in as when I upload, but I suppose it matters. :) The dist URL is the better one regardless, so I've changed them all over. If you click on the 1.49 link, it does show you that 2.1.0 is the latest, so that's something. I think I'll kick out another release with the URL fixes. Thanks! - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200802182332 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAke6W9AACgkQvJuQZxSWSsgICgCfVNdtvT0cK50oYnJsZyUfvCPW mfoAnRYp8OQe8QjPlfLjgLZSO0d03cri =XnNJ -----END PGP SIGNATURE-----
