DBD::PgPP is a Pure Perl client interface for the PostgreSQL database.
It implements the PostgreSQL client/server network protocol and doesn't
need an external PostgreSQL client library like "libpq" for it to work.
Consequently, it allows one to connect to a PostgreSQL server from
operating systems to which PostgreSQL has not been ported.
Module XBase provides access to XBase (dBase, Fox*) database files,
namely dbf, dbt, fpt, ndx, ntx, mdx, idx and cdx. It provides native
Perl interface ($table->get_record, $table->update_record) to read
and write the tables. The index support is alpha and read only at the
moment.
Module DBD::XBase is a DBI driver that uses the XBase module
to work with the data, providing you with DBI compliant processing
interface and SQL commands ($dbh->prepare("SELECT * FROM TABLE")). As
an argument to DBI->connect, specify "dbi:XBase:$dir", where $dir is
the directory with the data files.
A DBI driver for the Cego database for Perl 5
Many more details are available at:
A database interface (DBI) definition for communication between R
and relational database management systems. All classes in this
package are virtual and need to be extended by the various R/DBMS
implementations.
DBI::Shell
==========
The DBI::Shell module (and dbish command, if installed) provide a
simple but effective command line interface for the Perl DBI
module.
Please note: DBI::Shell is very new, very experimental and very
subject to change. Your mileage will vary. Interfaces will change
with each release.
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.