Free dbi 0.254 software for linux

Email::Store::DBI is a Perl module for database backend to Email::Store.

SYNOPSIS

use Email::Store dbi:...;

This class is a subclass of Class::DBI and contains means for Email::Store-based programs to register what DSN they wish to use. It also provides for building database tables from schemas embedded in the DATA section of plug-in modules, using Class::DBI::DATA::Schema.

"Email::Store" is the ideal basis for any application which needs to deal with databases of email: archiving, searching, or even storing mail for implementing IMAP or POP3 servers.

"Email::Store" itself is a very lightweight framework, meaning it does not provide very much functionality itself; in effect, it is merely a Class::DBI interface to a database schema which is designed for storing email. Incidentally, if you dont know much about "Class::DBI", youre going to need to in order to get much out of this.

Despite its minimalist nature, "Email::Store" is incredibly powerful. Its power comes from its extensibility, through plugin modules and hooks which allow you to add new database tables and concepts to the system, and so access the mail store from a "different direction". In a sense, "Email::Store" is a blank canvas, onto which you can pick and choose (or even write!) the plugins which you want for your application.

For instance, the core "Email::Store::Entity" plugin module addresses the idea of "people" in the email universe, allowing you to search for mails to or from particular people; (despite their changing names or email addresses) "Email::Store::Thread" interfaces "Email::Store" to "Mail::Thread" allowing you to navigate mails by their position in a mail thread; the planned non-core "Email::Store::Plucene" module plugs into the indexing process and stores information about emails in a Plucene search index for quick retrieval later, and so on.

Oryx::DBI is a DBI Storage interface for Oryx.

SYNOPSIS

my $storage = Oryx::DBI->new;

$storage->connect([ dbi:Pg:dbname=mydb, $usname, $passwd]);
$storage->connect([ dbi:Pg:dbname=mydb, $usname, $passwd], $schema);

$storage->dbh;
$storage->db_name;
$storage->ping;
$storage->schema;
$storage->util;
$storage->set_util;
$storage->deploy_class;
$storage->deploy_schema;

DBI Storage interface for Oryx. You should not need to instantiate this directly, use Oryx->connect() instead.

DBIx::Wrapper library is a Perl module that serves as a wrapper around DBI, providing additional functionality and convenience methods.
Enhancements:
- This release adds convenience methods for generating CSV, XML, and bencoded strings from query results.
- The connect_from_config() method was added in version 0.23, allowing database connection parameters to be specified in a file rather than in your code.

DBD::Ingres contains a DBI driver for Ingres database systems.

SYNOPSIS

$dbh = DBI->connect("DBI:Ingres:$dbname", $user, $options, {AutoCommit=>0})
$sth = $dbh->prepare($statement)
$sth = $dbh->prepare($statement, {ing_readonly=>1})
$sth->execute
@row = $sth->fetchrow
$sth->finish
$dbh->commit
$dbh->rollback
$dbh->disconnect
...and many more

DBD::Ingres is a database driver for the perl DBI system that allows access to Ingres databases. It is built on top of the standard DBI extension and implements the methods that DBI requires.

This document describes the differences between the "generic" DBD and DBD::Ingres.

DBI::FAQ is a Perl module for the Frequently Asked Questions of the Perl5 Database Interface.

What is DBI, DBperl, Oraperl and *perl?

To quote Tim Bunce, the architect and author of DBI:

``DBI is a database access Application Programming Interface (API)
for the Perl Language. The DBI API Specification defines a set
of functions, variables and conventions that provide a consistent
database interface independant of the actual database being used.

In simple language, the DBI interface allows users to access multiple database types transparently. So, if you connecting to an Oracle, Informix, mSQL, Sybase or whatever database, you dont need to know the underlying mechanics of the 3GL layer. The API defined by DBI will work on all these database types.

A similar benefit is gained by the ability to connect to two different databases of different vendor within the one perl script, ie, I want to read data from an Oracle database and insert it back into an Informix database all within one program. The DBI layer allows you to do this simply and powerfully.

DBperl is the old name for the interface specification. Its usually now used to denote perl4 modules on database interfacing, such as, oraperl, isqlperl, ingperl and so on. These interfaces didnt have a standard API and are generally not supported.

Heres a list of DBperl modules, their corresponding DBI counterparts and support information. Please note, the authors listed here generally do not maintain the DBI module for the same database. These email addresses are unverified and should only be used for queries concerning the perl4 modules listed below. DBI driver queries should be directed to the dbi-users mailing list.

However, some DBI modules have DBperl emulation layers, so, DBD::Oracle comes with an Oraperl emulation layer, which allows you to run legacy oraperl scripts without modification. The emulation layer translates the oraperl API calls into DBI calls and executes them through the DBI switch.

Heres a table of emulation layer information:

Module Emulation Layer Status
------ --------------- ------
DBD::Oracle Oraperl Complete
DBD::Informix Isqlperl Under development
DBD::Ingres Ingperl Complete?
DBD::Sybase Sybperl Working? ( Needs verification )
DBD::mSQL Msqlperl Experimentally released with
DBD::mSQL-0.61

The Msqlperl emulation is a special case. Msqlperl is a perl5 driver for mSQL databases, but does not conform to the DBI Specification. Its use is being deprecated in favour of DBD::mSQL. Msqlperl may be downloaded from CPAN via:

http://www.perl.com/cgi-bin/cpan_mod?module=Msqlperl

DBD::RAM is a DBI driver for files and data structures.

SYNOPSIS

use DBI;
my $dbh = DBI->connect(DBI:RAM:,usr,pwd,{RaiseError=>1});
$dbh->func({
table_name => my_phrases,
col_names => id,phrase,
data_type => PIPE,
data_source => [ ],
}, import );
print $dbh->selectcol_arrayref(qq[
SELECT phrase FROM my_phrases WHERE id = 1
])->[0];
__END__
1 | Hello, New World
2 | Some other Phrase

This sample creates a database table from data, uses SQL to make a selection from the database and prints out the results. While this table is in-memory only and uses pipe "delimited" formating, many other options are available including local and remote file access and many different data formats.

DBD::RAM allows you to import almost any type of Perl data structure into an in-memory table and then use DBI and SQL to access and modify it. It also allows direct access to almost any kind of file, supporting SQL manipulation of the file without converting the file out of its native format.

The module allows you to prototype a database without having an rdbms system or other database engine and can operate either with or without creating or reading disk files. If you do use disk files, they may, in most cases, either be local files or any remote file accessible via HTTP or FTP.

guile-dbi is a database generic interface. The main lib provide a way to use dbds (data base drivers) which are linked at run-time (like perl dbi or php or...).
This provide a very flexible way to use guile scheme implementation for db works. Now, implemented main dbi interface lib, mysql and postgres plugins... In near future more drivers will be available.
Enhancements:
- The API has been upgraded to Guile 1.8.

Bundle::DBI is a bundle to install DBI and required modules.

SYNOPSIS

perl -MCPAN -e install Bundle::DBI

CONTENTS

DBI - for to get to know thyself
DBI::Shell 11.91 - the DBI command line shell
Storable 2.06 - for DBD::Proxy and DBI::ProxyServer
Net::Daemon 0.37 - for DBD::Proxy and DBI::ProxyServer
RPC::PlServer 0.2016 - for DBD::Proxy and DBI::ProxyServer
DBD::Multiplex 1.19 - treat multiple db handles as one

This bundle includes all the modules used by the Perl Database Interface (DBI) module, created by Tim Bunce.

A Bundle is a module that simply defines a collection of other modules. It is used by the CPAN module to automate the fetching, building and installing of modules from the CPAN ftp archive sites.

This bundle does not deal with the various database drivers (e.g. DBD::Informix, DBD::Oracle etc), most of which require software from sources other than CPAN. Youll need to fetch and build those drivers yourself.