Ports Search

The object produced by Data::Pageset can be used to create page navigation, it inherits from Data::Page and has access to all methods from this object. In addition it also provides methods for dealing with set of pages, so that if there are too many pages you can easily break them into chunks for the user to browse through. You can even choose to view page numbers in your set in a 'sliding' fassion. The object can easily be passed to a templating system such as Template Toolkit or be used within a script.

The Genezzo modules implement a hierarchy of persistent hashes using a fixed amount of memory and disk. This system is designed to be easily configured and extended with custom functions, persistent storage representations, and novel data access methods. In its current incarnation it supports a subset of SQL and a partial DBI interface.

GitDDL::Migrator is database migration utility extended GitDDL. Extended features are: - save migration history - rollback to previous version - specify version - specify SQL (sometimes SQL::Translator's output is wrong) - check differences from versioned SQL and real database

This is database migration helper module for users who manage database schema version by single .sql file in git repository. By using this module, you can deploy .sql to database, check sql version between database and .sql file, make diff between them, and apply alter table to database.

This perl module constructs a graph for a database showing tables and connecting them if they are related. While or after constructing the object, pass an open database handle, then call `graph_tables' to determine database metadata and construct a GraphViz graph from the table and field information.

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.

his module contains a function to return an iterator (see the Iterator module) that returns the rows of a database query, one at a time. This is marginally more useful than simply calling prepare and execute, and then repeatedly calling fetchrow_hashref; since this one function bundles up the calls to all three of those DBI methods. But the real usefulness of this interface is that it can be chained together with other Iterator functions. The "idb_rows" iterator has the same interface as any other interface, making it interchangeable with iterators of any other source (for example, files), and usable with the iterator manipulation functions in the Iterator::Util module.

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.

This module wraps around the MLDBM interface, by handling concurrent access to MLDBM databases with file locking, and flushes i/o explicity per lock/unlock. The new [Read]Lock()/UnLock() API can be used to serialize requests logically and improve performance for bundled reads & writes.

MLDBM - store multi-level hash structure in single level tied hash This module, intended primarily for use with DBM packages, can serve as a transparent interface to any TIEHASH package that must be used to store arbitrary perl data, including nested references. It works by converting the values in the hash that are references, to their string representation in perl syntax. When using a DBM database, it is this string that gets stored.