AnyEvent-DBI
view release on metacpan - search on metacpan
view release on metacpan or search on metacpan
returned, but is postponed for "timeout" seconds each time more data is
returned from the server. If the timer ever goes off then a fatal error is
generated. If you have an C<on_error> handler installed, then it will be
called, otherwise your program will die().
When altering your databases with timeouts it is wise to use
transactions. If you quit due to timeout while performing insert, update
or schema-altering commands you can end up not knowing if the action was
submitted to the database, complicating recovery.
Timeout errors are always fatal.
=back
Any additional key-value pairs will be rolled into a hash reference
and passed as the final argument to the C<< DBI->connect (...) >>
call. For example, to suppress errors on STDERR and send them instead to an
AnyEvent::Handle you could do:
$dbh = new AnyEvent::DBI
"DBI:mysql:test;mysql_read_default_file=/root/.my.cnf", "", "",
fatal error is generated. If you have an "on_error" handler
installed, then it will be called, otherwise your program will
die().
When altering your databases with timeouts it is wise to use
transactions. If you quit due to timeout while performing
insert, update or schema-altering commands you can end up not
knowing if the action was submitted to the database,
complicating recovery.
Timeout errors are always fatal.
Any additional key-value pairs will be rolled into a hash reference
and passed as the final argument to the "DBI->connect (...)" call.
For example, to suppress errors on STDERR and send them instead to
an AnyEvent::Handle you could do:
$dbh = new AnyEvent::DBI
"DBI:mysql:test;mysql_read_default_file=/root/.my.cnf", "", "",
PrintError => 0,
on_error => sub {
view all matches for this distributionview release on metacpan - search on metacpan
( run in 0.622 second using v1.00-cache-2.02-grep-82fe00e-cpan-f5108d614456 )