new

Instantiates the Storage object.

set_schema

connected

disconnect

ensure_connected

throw_exception

txn_do

Arguments: $coderef, @coderef_args?

Return Value: The return value of $coderef

Executes $coderef with (optional) arguments @coderef_args atomically, returning its result (if any). If an exception is caught, a rollback is issued and the exception is rethrown. If the rollback fails, (i.e. throws an exception) an exception is thrown that includes a "Rollback failed" message.

For example,

  my $author_rs = $schema->resultset('Author')->find(1);
  my @titles = qw/Night Day It/;

  my $coderef = sub {
    # If any one of these fails, the entire transaction fails
    $author_rs->create_related('books', {
      title => $_
    }) foreach (@titles);

    return $author->books;
  };

  my $rs;
  try {
    $rs = $schema->txn_do($coderef);
  } catch {
    my $error = shift;
    # Transaction failed
    die "something terrible has happened!"
      if ($error =~ /Rollback failed/);          # Rollback failed

    deal_with_failed_transaction();
  };

In a nested transaction (calling txn_do() from within a txn_do() coderef) only the outermost transaction will issue a "txn_commit", and txn_do() can be called in void, scalar and list context and it will behave as expected.

Please note that all of the code in your coderef, including non-DBIx::Class code, is part of a transaction. This transaction may fail out halfway, or it may get partially double-executed (in the case that our DB connection failed halfway through the transaction, in which case we reconnect and restart the txn). Therefore it is best that any side-effects in your coderef are idempotent (that is, can be re-executed multiple times and get the same result), and that you check up on your side-effects in the case of transaction failure.

txn_begin

See the preferred "txn_do" method, which allows for an entire code block to be executed transactionally.

txn_commit

It does not perform an actual storage commit unless there's a DBIx::Class transaction currently in effect (i.e. you called "txn_begin").

txn_rollback

svp_begin

Created a new savepoint using the name provided as argument. If no name is provided, a random name will be used.

svp_release

Release the savepoint provided as argument. If none is provided, release the savepoint created most recently. This will implicitly release all savepoints created after the one explicitly released as well.

svp_rollback

Rollback to the savepoint provided as argument. If none is provided, rollback to the savepoint created most recently. This will implicitly release all savepoints created after the savepoint we rollback to.

txn_scope_guard

 my $txn_guard = $storage->txn_scope_guard;

 $result->col1("val1");
 $result->update;

 $txn_guard->commit;

If an exception occurs, or the guard object otherwise leaves the scope before "$txn_guard->commit" is called, the transaction will be rolled back by an explicit "txn_rollback" call. In essence this is akin to using a "txn_begin"/"txn_commit" pair, without having to worry about calling "txn_rollback" at the right places. Note that since there is no defined code closure, there will be no retries and other magic upon database disconnection. If you need such functionality see "txn_do".

sql_maker

debug

This is the equivalent to setting "DBIC_TRACE" in your shell environment.

debugfh

If the currently set "debugobj" does not have a "debugfh" method, caling this is a no-op.

debugobj

debugcb

See "debugobj" for a better way.

cursor_class

deploy

connect_info

This is normally accessed via "connection" in DBIx::Class::Schema, which encapsulates its argument list in an arrayref before calling "connect_info" here.

select

insert

update

delete

select_single

columns_info_for

DBIC_TRACE

If the value is of the form "1=/path/name" then the trace output is written to the file "/path/name".

This environment variable is checked when the storage object is first created (when you call connect on your schema). So, run-time changes to this environment variable will not take effect unless you also re-connect on your schema.

DBIC_TRACE_PROFILE

DBIX_CLASS_STORAGE_DBI_DEBUG