Changes for version 0.42 - 2010-12-17
- If a catch block died, the exception was not being propagated. That is, if a catch block threw an exception, DBIx::Connector ate it, and any calling code would not be able to catch it. This was a pretty serious bug; upgrading is strongly recommended for anyone using catch blocks.
- When `run()`, `txn()`, or `svp()` was called recursively from within a second fixup execution, it was not respecting the fact that it was recursive and could try to start a transaction again. This happened *only* when a fixup run found that the database was disconnected and successfully re-connected, so it's a pretty rare condition.
Modules
Fast, safe DBI connection and transaction management
Database-specific connection interface
Microsoft SQL Server-specific connection interface
Oracle-specific connection interface
PostgreSQL-specific connection interface
SQLite-specific connection interface
MySQL-specific connection interface
Provides
in lib/DBIx/Connector.pm
in lib/DBIx/Connector/Driver.pm
in lib/DBIx/Connector/Driver.pm
in lib/DBIx/Connector/Driver.pm