The Perl 5 module DBICx::Deploy deploys a DBIx::Class schema to a
database. A command line script, dbicdeploy, is provided.
The Perl 5 module DBICx::MapMaker automatically creates a DBIx::Class
result source for "many to many" relationship.
Just some syntax sugar for your DBIx::Class applications. This was originally
created to remove code duplication between Dancer::Plugin::DBIC and
Dancer2::Plugin::DBIC.
The Perl 5 module DBICx::TestDatabase creates a temporary SQLite
database, deploys your DBIC schema, and then connects to it. This
lets you easily test your DBIC schema. Since you have a fresh
database for every test, you don't have to worry about cleaning up
after your tests, ordering of tests affecting failure, etc.
Wrap all inserts into transactions.
DBIx::Abstract - DBI SQL abstraction.
This module provides methods for doing manipulating database tables
This module provides methods retrieving and storing data in SQL
databases. It provides methods for all of the more important SQL
commands (like SELECT, INSERT, REPLACE, UPDATE, DELETE).
It endeavors to produce an interface that will be intuitive to those
already familiar with SQL.
Notable features include:
* data_source generation for some DBD drivers.
* Can check to make sure the connection is not stale and reconnect
if it is.
* Controls statement handles for you.
* Can delay writes.
* Generates complex where clauses from hashes and arrays.
* Shortcuts (convenience functions) for some common cases. (Like
select_all_to_hashref.)
This class provides application developers with an abstraction class
a level away from DBI, that allows them to write an application
that works on multiple database platforms. The idea isn't to take
away the responsibility for coding different SQL on different
platforms, but to simply provide a platform that uses the right
class at the right time for whatever DB is currently in use.
The purpose of DBIx::Browse is to handle the browsing of relational
tables.
DBIx::Browse transparently translates SELECTs, UPDATEs, DELETEs and
INSERTs from the desired "human view" to the values needed for the ta-
ble. This is the case when you have related tables (1 to n) where the
detail table has a reference (FOREIGN KEY) to a generic table (i.e.
Customers and Bills) with some index (tipically an integer).
Philip M. Gollucci <philip@p6m7g8.com>
DBIx::Connector provides a simple interface for fast and safe DBI
connection and transaction management. Connecting to a database can
be expensive; you don't want your application to re-connect every time
you need to run a query. The efficient thing to do is to hang on to a
database handle to maintain a connection to the database in order to
minimize that overhead. DBIx::Connector lets you do that without
having to worry about dropped or corrupted connections.
DBIx::ContextualFetch redefines some of the various fetch methods to
add context sensitivity.