-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> OK, thanks. we should mothball the gborg repo so people don't waste their > time. > > When do we intend to stop support for versions older than 7.4? 7.2 is > genuinely dead, and 7.3 is on its last legs. Is there any reason to > support these in new releases of DBD::Pg? I just returned from a very long car trip, and one of the many things I was thinking over was this very issue. I'm strongly leaning towards not supporting 7.3 at all, beginning with the next version, unless someone on this list can give a very strong reason for keeping it. Not only is 7.3 ancient at this point, but there were major changes made from 7.3 to 7.4 which not only makes our code more complicated, but almost all of the recent additions to DBD::Pg are things that are not even supported in 7.3. Last time I brought this up on the list there were some strong disagreements about ending 7.3 support, but I don't see that happening this time barring some insanely good reason I'm overlooking. :) I should also have time in the next couple weeks to get going again in earnest on DBD::Pg - my tentative goal is a new version at the end of January. Any feature requests, patches, etc. please speak up now. Current things off the top of my head already scheduled: COPY overhaul, full array support, statistics info support, utf audit/overhaul, support for other "default" variables (e.g. CURRENT_TIMESTAMP). Possible future stuff: asynchronous statements, better function support, log/conf file parsing. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200612311445 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFFmBQCvJuQZxSWSsgRAgwOAJ0XJi38KbPlhKkNzWvkLJbv+tc1DACdE9GD lyGHBDgKrY52Q8nUaltlO8U= =DyIP -----END PGP SIGNATURE-----
