Skip Menu |

This queue is for tickets about the DateTime-Format-SQLite CPAN distribution.

Report information
The Basics
Id: 52468
Status: resolved
Worked: 2 hours (120 min)
Priority: 0/
Queue: DateTime-Format-SQLite

People
Owner: CFAERBER [...] cpan.org
Requestors: GRAF [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in:
  • 0.10
  • 0.01_20090913
Fixed in: 0.11



Subject: Test failure
Fails with current DateTime 0.52 probably because starting with DateTime 0.52 new() accepts integer values only. t/parse.t ........ 1/30 The 'second' parameter ("4.123") to DateTime::new did not pass the 'an integer between 0 and 61' callback at /opt/perl/5.10.1/lib/site_perl/x86_64-linux/DateTime.pm line 176 DateTime::new(undef, 'hour', 2, 'minute', 3, 'second', 4.123, 'month', 09, ...) called at /opt/perl/5.10.1/lib/site_perl/DateTime/Format/Builder/Parser/Regex.pm line 135 DateTime::Format::Builder::Parser::Regex::make('DateTime::Format::Builder::Parser::Regex=HASH(0xe4da00)', '-2-09-13 2:3:4.123', undef, 'HASH(0xe2f490)') called at /opt/perl/5.10.1/lib/site_perl/DateTime/Format/Builder/Parser/generic.pm line 123 DateTime::Format::Builder::Parser::generic::__ANON__('DateTime::Format::SQLite', '-2-09-13 2:3:4.123', 'HASH(0xdba1b8)') called at /opt/perl/5.10.1/lib/site_perl/DateTime/Format/Builder/Parser.pm line 450 DateTime::Format::Builder::Parser::__ANON__('DateTime::Format::SQLite', '-2-09-13 2:3:4.123') called at /opt/perl/5.10.1/lib/site_perl/DateTime/Format/Builder/Parser.pm line 85 DateTime::Format::Builder::Parser::parse('DateTime::Format::Builder::Parser=HASH(0xe4d7d8)', 'DateTime::Format::SQLite', '-2-09-13 2:3:4.123') called at /opt/perl/5.10.1/lib/site_perl/DateTime/Format/Builder.pm line 189 DateTime::Format::Builder::__ANON__('DateTime::Format::SQLite', '-2-09-13 2:3:4.123') called at t/parse.t line 91
On So. 06. Dez. 2009, 06:12:16, GRAF wrote: Show quoted text
> Fails with current DateTime 0.52 > probably because starting with DateTime 0.52 new() accepts integer > values only.
Thanks for reporting this bug. I've just released v0.11, which fixes this. Claus