Skip Menu |
 

This queue is for tickets about the SQL-Statement CPAN distribution.

Report information

Subject: bugreport
Date: Mon, 4 Jan 2010 15:55:13 +0100
To: bug-SQL-Statement [...] rt.cpan.org
From: Matthäus Kiem <matthaeuskiem [...] gmail.com>
Download (untitled) / with headers
text/plain 841b
Hello, as attachments I send you scripts. In these scripts I try to explain bugs. Please don't shoot me, if I have overlooked something and my bugs are not bugs. My SQL::Statement::VERSION is 1.23 The rest: Perl : 5.010000 (x86_64-linux-thread-multi) OS : linux (2.6.31) DBI : 1.609 DBD::Sponge : 12.010002 DBD::SQLite : 1.25 DBD::Proxy : 0.2004 DBD::Gofer : 0.011565 DBD::File : 0.37 DBD::ExampleP : 12.010007 DBD::DBM : 0.03 DBD::CSV : 0.26 Greetings Matthäus
Download between.pl
text/x-perl 1020b

Message body is not shown because sender requested not to inline it.

Download distinct.pl
text/x-perl 1.1k

Message body is not shown because sender requested not to inline it.

Download regex.pl
text/x-perl 771b

Message body is not shown because sender requested not to inline it.

Download rowhash1.pl
text/x-perl 1.5k

Message body is not shown because sender requested not to inline it.

Download rowhash2.pl
text/x-perl 1.2k

Message body is not shown because sender requested not to inline it.

Download substring.pl
text/x-perl 1.4k

Message body is not shown because sender requested not to inline it.

Download trim.pl
text/x-perl 1.2k

Message body is not shown because sender requested not to inline it.

Hi Matthias,

there is no reason to shoot you, but if you request it: *peng* you are dead, game over :)

Anyway - some of the errors you reported are fixed in the repository, some are in progress and with some you hit a point I detected while I was working on Bug #52356 from Detlef.
For the next time please for each bug you've detected:
1) Check whether any open bug still contains the issue you want to report - and possibly update it (with a 'me too' or better a test code - as you provided)
2) Open a new bug report for exact the issue you want to report - not 2, not 3 - one.
3) Please add a short description of the issue in the subject line.

For this time, I reject the entire report. This doesn't mean, that I wont care of the bugs you've reported. I will care and I will care for next release.
But it's impossible for me to track all 7 reports in one RT. If you rate one of them (or more) is worthwhile to be tracked, open a new report exact for the wanted issue.

Best regards,
Jens


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.