Ports Search

Customizable DBI

DBIx::DBHResolver resolves database connection on the environment has many database servers. The resolution algorithm is extensible and pluggable, because of this you can make custom strategy module easily. This module can retrieve DBI's database handle object or connection information (data source, user, credential...) by labeled name and treat same cluster consists many nodes as one labeled name, choose fetching strategy.

DBIx::Dump allows you to easily dump database data, retrieved using DBI, into a variety of formats including Excel, CSV, etc...

DBIx::Ease is intended to allow less-code DBI interactions. Upon creation of a new DBIx::Ease object you should pass the portion of the DSN (Data Source Name) common to all connections the object is supposed to store. Replace the variable portions with '<databasename>'. Whenever you wish to make only one connection you may enter the complete DSN, also when you want to make connections with the same source but as different users, then call exec() with different names of your choice as initial argument.

Get information from $dbh.

Detect what database you are connected to.

DBIx::Log4perl is a wrapper over DBI which adds logging of your DBI activity via a Log::Log4perl handle. Log::Log4perl has many advantages for logging but the ones probably most attractive are: The ability to turn logging on or off or change the logging you see without changing your code. Different log levels allowing you to separate warnings, errors and fatals to different files.

The DBIx::MySQLSequence package implements an emulation layer that provides "real" sequences on MySQL. The module works by creating a "sequence table", a single table where each record represents a single sequence, and performing some "magic" MySQL specific SQL to ensure the sequences will work correctly.

DBIx::NoSQL is a layer over DBI that presents a NoSQLish way to store and retrieve data. It does this by using a table called __Store__. Once connected to a database, it will detect if this table is missing and create it if necessary. When writing data to the store, the data (a HASH reference) is first serialized using JSON and then inserted/updated via DBIx::Class to (currently) an SQLite backend. Retrieving data from the store is done by key lookup or by searching an SQL-based index. Once found, the data is deserialized via JSON and returned.

This module keeps track of database passwords.