Free dbd sqlite 1.12 software for linux

DBD::SQLite is a Self Contained RDBMS in a DBI Driver.
SYNOPSIS
use DBI;
my $dbh = DBI->connect("dbi:SQLite:dbname=dbfile","","");
SQLite is a public domain RDBMS database engine that you can find at http://www.hwaci.com/sw/sqlite/.
Rather than ask you to install SQLite first, because SQLite is public domain, DBD::SQLite includes the entire thing in the distribution. So in order to get a fast transaction capable RDBMS working for your perl project you simply have to install this module, and nothing else.
SQLite supports the following features:
- Implements a large subset of SQL92
See http://www.hwaci.com/sw/sqlite/lang.html for details.
- A complete DB in a single disk file
Everything for your database is stored in a single disk file, making it easier to move things around than with DBD::CSV.
- Atomic commit and rollback
Yes, DBD::SQLite is small and light, but it supports full transactions!
- Extensible
User-defined aggregate or regular functions can be registered with the SQL parser.
Theres lots more to it, so please refer to the docs on the SQLite web page, listed above, for SQL details. Also refer to DBI for details on how to use DBI itself.

DBD::mSQL / DBD::mysql is a Perl module with mSQL and mysql drivers for the Perl5 Database Interface (DBI).

SYNOPSIS

use DBI;

$driver = "mSQL"; # or "mSQL1";
$dsn = "DBI:$driver:database=$database;host=$hostname";

$dbh = DBI->connect($dsn, undef, undef);

or

$driver = "mysql";
$dsn = "DBI:$driver:database=$database;host=$hostname;port=$port";

$dbh = DBI->connect($dsn, $user, $password);


$drh = DBI->install_driver("mysql");
@databases = $drh->func($host, $port, _ListDBs);
@tables = $dbh->func( _ListTables );

$sth = $dbh->prepare("SELECT * FROM foo WHERE bla");
or
$sth = $dbh->prepare("LISTFIELDS $table");
or
$sth = $dbh->prepare("LISTINDEX $table $index");
$sth->execute;
$numRows = $sth->rows;
$numFields = $sth->{NUM_OF_FIELDS};
$sth->finish;

$rc = $drh->func(createdb, $database, $host, $user, $password, admin);
$rc = $drh->func(dropdb, $database, $host, $user, $password, admin);
$rc = $drh->func(shutdown, $host, $user, $password, admin);
$rc = $drh->func(reload, $host, $user, $password, admin);

$rc = $dbh->func(createdb, $database, admin);
$rc = $dbh->func(dropdb, $database, admin);
$rc = $dbh->func(shutdown, admin);
$rc = $dbh->func(reload, admin);

EXAMPLE

#!/usr/bin/perl

use strict;
use DBI();

# Connect to the database.
my $dbh = DBI->connect("DBI:mysql:database=test;host=localhost",
"joe", "joes password",
{RaiseError => 1});

# Drop table foo. This may fail, if foo doesnt exist.
# Thus we put an eval around it.
eval { $dbh->do("DROP TABLE foo") };
print "Dropping foo failed: $@n" if $@;

# Create a new table foo. This must not fail, thus we dont
# catch errors.
$dbh->do("CREATE TABLE foo (id INTEGER, name VARCHAR(20))");

# INSERT some data into foo. We are using $dbh->quote() for
# quoting the name.
$dbh->do("INSERT INTO foo VALUES (1, " . $dbh->quote("Tim") . ")");

# Same thing, but using placeholders
$dbh->do("INSERT INTO foo VALUES (?, ?)", undef, 2, "Jochen");

# Now retrieve data from the table.
my $sth = $dbh->prepare("SELECT * FROM foo");
$sth->execute();
while (my $ref = $sth->fetchrow_hashref()) {
print "Found a row: id = $ref->{id}, name = $ref->{name}n";
}
$sth->finish();

# Disconnect from the database.
$dbh->disconnect();

DBD::mysql and DBD::mSQL are the Perl5 Database Interface drivers for the mysql, mSQL 1.x and mSQL 2.x databases. The drivers are part of the Msql-Mysql-modules package.
In other words: DBD::mSQL and DBD::mysql are an interface between the Perl programming language and the mSQL or mysql programming API that come with the mSQL any mysql relational database management systems. Most functions provided by the respective programming APIs are supported. Some rarely used functions are missing, mainly because noone ever requested them.

SableVM is a robust, extremely portable, efficient, and specifications-compliant Java virtual machine that aims to be easy to maintain and to extend.
It features a state-of-the-art and efficient interpreter engine. Its source code is very accessible and easy to understand. It also has many robustness features that have been the object of careful design.
SableVM is a clean-room implementation of the publicly available specifications.
Main features:
- Clean code, with minimal duplication, thanks to a set of easy-to-use indent-friendly m4 macros.
- Modularity, making it ideal for research into different implementations of VM components.
- Standards compliance (C, POSIX, JVM, JNI, JLS).
- Three different interpreter engines, of which the basic switch interpreter is perfect for debugging, and the inlined-threaded interpreter is competitively fast. See [Execution Engines]?.
- A nice development environment, thanks to the above features. New contributors can start grokking it easily.
- Use of the latest GNU Classpath. We frequently synchronize with the GNU Classpath CVS.
- Portability (record time is 1 hour for a new port).
- Permissive LGPL license.
- A retargettable just-in-time compiler, SableJIT, which currently runs on ppc, x86, and sparc. The initial implementation is almost ready.
- Proper implementation of the invocation interface, which makes it possible to execute Java code from an application written in a different language. SableVM was designed so that extending it to follow the full specifications is straightforward, and allows for many virtual machines to be created, run, and destroyed within a single process (still not fully complete). This is something that the official Sun implementation does not provide.

ByteName project is a tool that for each byte of the input prints a line consisting of the byte offset, the hex value of the byte, the octal value of the byte, and its description in Latin-1, Latin-2, WinLatin1, WinLatin2, or EBCDIC.
A command line flag suppresses printing of bytes within the ASCII range which is useful for locating stray non-ASCII codes.
The available encodings are:
- Latin-1 (ISO-8859-1)
- Latin-2 (ISO-8859-2)
- WinLatin1 (Microsoft Codepage 1252
- WinLatin2 (Microsoft Codepage 1250
- EBCDIC-037 (IBM Codepage 037)
Enhancements:
- This release adds MS DOS Codepages 437 and 850.
- Bugs in MS Windows Codepage 1252 were fixed.

mod_dbd_pgsql is a DBD Driver module for PostgreSQL.

apr_dbd

The apr_dbd framework presents a common API for different SQL database engines. The API is documented in apr_dbd.h.

DBD Drivers

APR DBD Drivers are currently available for MySQL and PostgreSQL. The apr_dbd architecture supports dynamic loading of database driver modules, so that new drivers can be installed at any time, without any requirement to recompile APR (provided the platform supports dynamic loading).

mod_dbd

mod_dbd presents the API for Apache modules, and deals with managing database connections efficiently for both threaded and non-threaded MPMs.

mod_sql

mod_sql is an XML Namespace Module that builds on mod_dbd to implement SQL handling in XML applications with mod_publisher or mod_xmlns.

sixbs is a library capable of writing and reading beans to and from XML using their public properties. sixbs is especially suited for writing configuration data or sending data over the network.

Contrary to normal Java serialization it is readable (i.e., you can easily edit it with your favourite text editor), and it is independent from class versions.

DBD::Teradata is Perl module with a DBI driver for Teradata.

SYNOPSIS

use DBI;

$dbh = DBI->connect(dbi:Teradata:hostname, user, password);
See DBI for more information.

Refer to the included tdatdbd.html.

Xoscope (or oscope) is a digital oscilloscope using input from a sound card or EsounD and/or a ProbeScope/osziFOX.

Xoscopes features include 8 simultaneous signal displays, 1 us/div to 2 s/div time scale, built-in and external math functions including inverse, sum, diff, avg, xy, and FFT, 23 memory buffers, 5 automatic measurements, and file save/load.