DBD::mysql 4.015 Released

2010-07-09 Thread Patrick Galbraith
I'm glad to let everyone out in Perl Land know that DBD::mysql 4.015 is released. Per the changelog: * BUG #56664 fixed t/40blobs.t skip_all logic (W. Phillip Moore) * BUG #57253 Fixed iteration past end of string (crash). (Chris Butler) * Added a new parameter for old behavior- mysql_bind_comm

Re: Take care with version numbers (eg DBD::Pg)

2010-07-09 Thread David E. Wheeler
On Jul 9, 2010, at 5:52 AM, Tim Bunce wrote: >> In principle, and as an end-user I would wholeheartedly agree, but the >> way CPAN /and/ CPANTESTERS is currently set up, having _XX support is a >> huge win. > > Agreed. But there's no need to use them *in modules*. > > The dev releases of DBI 1.

Re: DBD::Oracle DRCP_1.25

2010-07-09 Thread luben karavelov
On 9.07.2010 00:41, John Scoles wrote: Hi Luben I have incorporated your patch into the DRCP branch and I have also merged that branch back into trunk for any testing that you will be doing I would try it with the Trunk which you can find here http://svn.perl.org/modules/dbd-oracle/trunk I we

Re: Take care with version numbers (eg DBD::Pg)

2010-07-09 Thread Tim Bunce
On Fri, Jul 09, 2010 at 07:47:00AM +0200, H.Merijn Brand wrote: > On Thu, 8 Jul 2010 15:56:38 -0700, "David E. Wheeler" > wrote: > > > Underscores should be banned from version numbers. Full stop. > > In principle, and as an end-user I would wholeheartedly agree, but the > way CPAN /and/ CPANTE

Re: can not install latest DBI developer release with cpan on Win32

2010-07-09 Thread Martin J. Evans
Steffen Winkler wrote: > The installation is ok now: > - ActivePerl-5.12.1.1201-MSWin32-x86-292674.msi installed > - run cpan install TIMB/DBI-1.611_93.tar.gz > CPAN output: > > It looks like you don't have a C compiler and make utility installed. Trying > to install dmake and the MinGW gcc compi

Re: Take care with version numbers (eg DBD::Pg)

2010-07-09 Thread Jens Rehsack
On 07/08/10 17:08, David E. Wheeler wrote: On Jul 8, 2010, at 9:38 AM, Jens Rehsack wrote: Looks like it should have been 2.6.0: 2.6.0 = 2.006001 2.17.1 = 2.017001 2.006001< 2.017001 Version number suck. And clearly, three-version numbers suck harder. I think, the best way out woul