Ports Search

ldb is a LDAP-like embedded database. ldb provides a fast database with an LDAP-like API designed to be used within an application. In some ways it can be seen as a intermediate solution between key-value pair databases and a real LDAP database.

This is libsdb, the simple database library, which provides a way to support multiple database management systems in an application with negligeable overhead, in terms of code as well as system resources. Supported databases: - Lago - Mysql - Sqlite - Mimer - Postgresql - Oracle - Gdbm

The Perl script mysql2pgsql can be used to convert MySQL database dumps to a PostgreSQL-compatible format (so the data can be imported into PostgreSQL). This can be useful if you are switching from MySQL to PostgreSQL and you have quite a bit of data in your MySQL databases.

This is an extension to Class::DBI that currently implements: * A sequence fix for Oracle databases. * Automatic column name discovery. * Automatic primary key detection. * Sequence name guessing. * Proper aliasing of reserved words. Instead of setting Class::DBI as your base class, use this.

DBD::LDAP is a DBI extension module adding an SQL database interface to standard LDAP databases to Perl's database-independent database interface. You will need access to an existing LDAP database or set up your own using an LDAP server, ie. "OpenLDAP".

Dump fixtures from source database to filesystem then import to another database (with same schema) at any time. Use as a constant dataset for running tests against or for populating development databases when impractical to use production clones. Describe fixture set using relations and conditions based on your DBIx::Class schema.

This module implements an OO-interface to database schemas. Using this module, you can create a database schema with an OO Perl interface. You can read the schema from an existing database. You can save the schema to disk and restore it in a different process. Most importantly, DBIx::DBSchema can write SQL CREATE statements for different databases from a single source.

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.

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.