Constructor¶

"new"

  my $driver = DBIx::Connector::Driver->new( $driver );

Constructs and returns a driver object. Each driver class is implemented as a singleton, so the same driver object is always returned for the same driver. The "driver" parameter should be a Perl DBI driver name, such as "Pg" for DBD::Pg or "SQLite" for DBD::SQLite. If a subclass has been defined for $driver, then the object will be of that class. Otherwise it will be an instance of the driver base class.

Instance Methods¶

"ping"

  $driver->ping($dbh);

Calls "$dbh->ping". Override if for some reason the DBI driver doesn't do it right.

"begin_work"

  $driver->begin_work($dbh);

Calls "$dbh->begin_work". Override if for some reason the DBI driver doesn't do it right.

"commit"

  $driver->commit($dbh);

Calls "$dbh->commit". Override if for some reason the DBI driver doesn't do it right.

"rollback"

  $driver->rollback($dbh);

Calls "$dbh->rollback". Override if for some reason the DBI driver doesn't do it right.

"savepoint"

  $driver->savepoint($dbh, $name);

A no-op. Override if your database does in fact support savepoints. The driver subclass should create a savepoint with the given $name. See the implementations in DBIx::Connector::Driver::Pg and DBIx::Connector::Driver::Oracle for examples.

"release"

  $driver->release($dbh, $name);

A no-op. Override if your database does in fact support savepoints. The driver subclass should release the savepoint with the given $name. See the implementations in DBIx::Connector::Driver::Pg and DBIx::Connector::Driver::Oracle for examples.

"rollback_to"

  $driver->rollback_to($dbh, $name);

A no-op. Override if your database does in fact support savepoints. The driver subclass should rollback to the savepoint with the given $name. See the implementations in DBIx::Connector::Driver::Pg and DBIx::Connector::Driver::Oracle for examples.