Projects

IPC::Concurrency::DBI

Controls how many instances of an application run in parallel, using DBI as the IPC method.

Queue::DBI

Queue system with an emphasis on safety, using DBI as a storage system for queued data.

DBIx::ScopedTransaction

Scope database transactions on DBI handles in code, to detect and prevent issues with unterminated transactions.

Audit::DBI

dbix-timeout

This module provides a safe method of timing out DBI requests. An unsafe method is described in the DBI docs: http://search.cpan.org/~timb/DBI/DBI.pm#Signal_Handling_and_Canceling_Operations The problem with using POSIX sigaction() (the method described above) is that it relies on unsafe signals ... [More] to work. Unsafe signals are well known to cause instability. To understand why, imagine the DB client code is in the middle of updating some global state when the signal arrives. That global state could be left in an inconsitent state, just wait for the next time it is needed to cause problems. Since this will likely occur far from the cause, and only ocur rarely, it can be a very difficult problem to track down. Instead, this module:   - Forks a child process which sleeps for $timeout seconds.   - Runs your long-running query in the parent process.   - If the parent process finishes first it kills the child and     returns.   - If the child process wakes up it kills the parent's DB thread and     exits with a code so the parent knows it was timed out. NOTE: After this call your database connection may be killed even if no timeout occurred. This is due to a race condition - the child may wake up just as parent process finishes. Patches addressing this bug are welcome. Until this is fixed you should be ready to reconnect after call_with_timeout(). [Less]

DBIx::NinjaORM

Flexible Perl ORM for easy transitions from inline SQL to objects.