This plugin makes it very easy to create Dancer2 applications that
interface with databases. It automatically exports the keyword `schema`
which returns a DBIx::Class::Schema object. You just need to configure
your database connection information. For performance, schema objects
are cached in memory and are lazy loaded the first time they are accessed.
Ima::DBI attempts to organize and facilitate caching and more efficient
use of database connections and statement handles by storing DBI and SQL
information with your class (instead of as separate objects). This
allows you to pass around just one object without worrying about a trail
of DBI handles behind it.
Jifty::DBI deals with databases, so that you don't have to.
This module provides an object-oriented mechanism for retrieving and
updating data in a DBI-accesible database.
This module is the direct descendent of DBIx::SearchBuilder. If you're
familiar with SearchBuilder, Jifty::DBI should be quite familiar to you.
Oryx is an object persistence framework which supports both object-relational
mapping as well as DMB style databases and as such is not coupled with any
particular storage back-end. In other words, you should be able to
swap out an RDMBS with a DBM style database (and vice versa) without
changing your persistent classes at all.
The SQL::Statement module implements a small, abstract SQL engine. By
parsing an SQL query you create an SQL::Statement instance. This instance
offers methods for retrieving syntax, for WHERE clause and statement
evaluation. The implementation is designed to work with the DBI driver
DBD::CSV, and should be easily extensible.
Tangram is an object-relational mapper. It makes objects persist in relational
databases, and provides powerful facilities for retrieving and filtering them.
Tangram fully supports object-oriented programming, including polymorphism,
multiple inheritance and collections. It does so in an orthogonal fashion,
that is, it doesn't require your classes to implement support functions nor
inherit from a utility class.
DB_Pager retrieve and return information of database result sets.
This class handles all the stuff needed for displaying
paginated results from a database query of Pear DB.
including fetching only the needed rows and giving extensive information
for helping build an HTML or GTK query result display.
PEAR::DB_Sqlite_Tools is an object oriented interface to effectively
manage and backup Sqlite databases.It extends the existing functionality
by providing a comprehensive solution for database backup, live replication,
export in XML format, performance optmization and other functionalities like
the insertion and retrieval of encrypted data from an Sqlite database without
any external extension.
PEAR::MDB2_Schema enables users to maintain RDBMS independant schema
files in XML that can be used to create, alter and drop database entities
and insert data into a database. Reverse engineering database schemas from
existing databases is also supported. The format is compatible with both
PEAR::MDB and Metabase.
pgAdmin III is a comprehensive PostgreSQL database design and management
system for *nix and Windows systems. It is freely available under the
terms of the Artistic Licence and may be redistributed provided the terms
of the licence are adhered to. The project is managed by the pgAdmin
Development Team.