view release on metacpan or  search on metacpan

lib/DBI/BabyConnect.pm  view on Meta::CPAN

Because DBI::BabyConnect objects are live objects that are connected to data sources, programmers
can invoke methods to execute SQL transactions on the data sources.

After you have executed a SQL transaction with a DBI::BabyConnect object, usually DBI requires
that you end the transaction by committing if it passes, by rolling back or raising error if it
fails, by calling finish on the cursor, and by disconnecting the handle.

However DBI::BabyConnect objects are designed to be persisted and to be pooled
within an application. Programmers, 
do not need to call any of the functions aforementioned because 
DBI::BabyConnect will do that transparently for you. You use DBI::BabyConnect so that
you can work with an object whose connection is persisted to a data source, and
the object will do all clean up upon object destruction.

The following functions are provided so that if you chose to port an application that
uses DBI directly, you can easily make use of DBI::BabyConnect without making extensive changes
to the application.

=head2 commit

Call commit() on the handle open by DBI::BabyConnect object. This method is provided to ease