Skip Menu |

This queue is for tickets about the DBD-mysql CPAN distribution.

Report information
The Basics
Id: 15802
Status: resolved
Priority: 0/
Queue: DBD-mysql

Owner: Nobody in particular
Requestors: tyler [...]

Bug Information
Severity: (no value)
Broken in: 3.0002
Fixed in: (no value)

Subject: DBD::mysql doesn't always obey "PrintWarn" setting
Download (untitled) / with headers
text/plain 579b
DBD::mysql doesn't always seem to obey the "PrintWarn" option of DBI. For instance, I connected to my database with: my $dbh = DBI->connect( @args{'dsn','user','pass'}, { RaiseError => 0, PrintError => 0, PrintWarn => 0, AutoCommit => 1 } ) or die("Couldn't connect to database: ", DBI->errstr, "\n"); And I am still getting these messages: commit ineffective with AutoCommit enabled at migrate-database-schema line 96. Commmit ineffective while AutoCommit is on at migrate-database-schema line 96. It also seems odd that I get this message twice. Thanks, Tyler
Download (untitled) / with headers
text/plain 330b
The warning messages with commit spelled incorrectly were coming from DBD::mysql, and have been removed. That change will be in the next DBD::mysql release (probably 4.01). The correctly-spelled commit messages are coming from DBI itself, and their printing is controlled by the 'Warn' attribute, not the 'PrintWarn' attribute.

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

Please report any issues with to