The DBIx::SQLEngine class provides an extended interface for DBI
database handles, adding methods that support ad-hoc SQL generation and
query execution in a single call.
PR: 55129
Submitted by: Hansjoerg Pehofer <hansjoerg.pehofer@uibk.ac.at>
Class::DBI::Pg automate the setup of Class::DBI columns and
primary key for Postgres.
PR: 54725
Submitted by: Mathieu Arnold <m@absolight.net>
Approved by: fjoe (mentor) (implicit)
Class::DBI::SQLite is an extension to Class::DBI for
DBD::SQLite, which allows you to populate auto incremented row
id after insert.
PR: 54749
Submitted by: Mathieu Arnold <m@absolight.net>
Approved by: fjoe (mentor)
By taking the busy work out of using Class::DBI as you see fit,
your code becomes more useful by size. Most of us end up using
at least a couple Class::DBI extensions in our programs, and
it's just a pain. Enter the Swiss Army Knife.
PR: 54748
Submitted by: Mathieu Arnold <m@absolight.net>
Approved by: fjoe (mentor)
Class::DBI::Pager is a plugin for Class::DBI, which glues
Data::Page with Class::DBI.
PR: 54723
Submitted by: Mathieu Arnold <m@absolight.net>
Approved by: fjoe (mentor)
When searching through large amounts of data, it is often the
case that a result set is returned that is larger than we want
to display on one page. This results in wanting to page through
various pages of data. The maths behind this is unfortunately
fiddly, hence this module.
PR: 54720
Submitted by: Mathieu Arnold <m@absolight.net>
Approved by: fjoe (mentor)
Class::DBI::AbstractSearch is a Class::DBI plugin to glue
SQL::Abstract into
Class::DBI.
PR: 54714
Submitted by: Mathieu Arnold <m@absolight.net>
Approved by: fjoe (mentor)
PureDB is a portable and tiny set of libraries for creating
and reading constant databases. It manages data files that
contains text or binary key/data pairs of arbitrary sizes.
Lookups are very fast (normally only one disk access to
match a hash value), overhead is low (a database is 1028
bytes plus only 16 extra bytes per record), multiple
concurrent read access are supported, and databases can be
up to 4 Gb long, and they are portable across architectures.
PR: ports/48901
Submitted by: Sergei Kolobov <sergei@kolobov.com>
p5-Resource's DBI and Net::LDAP resources are from this
version on split into separate modules.
PR: ports/48000
Submitted by: Erwin Lansing <erwin@lansing.dk>
upgrade to the PostgreSQL 7.3 series and provide an update to the 7.2
series, 7.2.4. :~] This port _will_ be removed and should EOL'ed in
about 6 months time. Since there is no future for these bits, ignore their
heritage commit an orphan for the 7 series. See the postgresql7 port for
future and past bits. This port is only intended to serve as a means of
postponing an inevitable upgrade to recent release.
DBAs, please plan and begin upgrading to 7.3.X, the grass really is greener.
Release notes:
http://developer.postgresql.org/docs/postgres/release-7-2-4.html
PR: ports/48025
Submitted by: Palle Girgensohn <girgen@pingpong.net>
zodb3 is different from zodb which is already in the database
ports collection.
The ZODB package is a Python object persistence system. It
provides the Z Object Database separately from Zope so it
can be used in non-Zope related Python applications to
provide transparent object-oriented persistency.
PR: ports/46108
Submitted by: Martin Klaffenboeck <martin.klaffenboeck@gmx.at>
The goal of the PySQLite project is to develop a Python
extension for SQLite that conforms to the Python Database
API Specification 2.0. SQLite is a powerful embedded
relational database management system in a compact C library.
It offers support for a large subset of SQL92, multiple
tables, indices, transactions and triggers.
PR: ports/43571
Submitted by: Gerhard Häring <gerhard.haering@gmx.de>
When you've got one of those nasty self-referential tables
that you want to bust out into a tree, this is the module
to check out. Assuming there are no horribly broken nodes
in your tree and (heaven forbid) any circular references
PR: ports/47660
Submitted by: Philip M. Gollucci <philip@p6m7g8.com>
The purpose of DBIx::Browse is to handle the browsing of
relational tables.
DBIx::Browse transparently translates SELECTs, UPDATEs,
DELETEs and INSERTs from the desired "human view" to the
values needed for the ta- ble. This is the case when you
have related tables (1 to n) where the detail table has a
reference (FOREIGN KEY) to a generic table (i.e. Customers
and Bills) with some index (tipically an integer).
PR: ports/47624
Submitted by: Philip M. Gollucci <philip@p6m7g8.com>
This port can be useful those, who have to manage MySQL
remotely via web, but they don't want to install php for
phpMyAdmin. Unfortunately the license is not complete free:
You have to download yourself from the original distribution
site then you can freely use it, but you cannot redistribute.
PR: ports/38958
Submitted by: Janos Mohacsi <janos.mohacsi@bsd.hu>
