Free jdbc driver for mysql software for linux

Zmanda Recovery Manager for MySQL simplifies life of a database administrator who needs an easy to use yet flexible and robust backup and recovery solution for MySQL server. With ZRM for MySQL you can:
- Schedule full and incremental logical or raw backups of your MySQL database
- Perform backup that is the best match for your storage engine and your MySQL configuration
- Get e-mail notification about status of your backups
- Monitor and browse your backups
- Recover database easily to any point in time or to any particular transaction

HDBC ODBC Driver is the Haskell ODBC backend driver for HDBC. This driver has been tested on Windows and on Linux with unixODBC. It should also be compatible with iODBC, though this has not been tested. It should be portable to any platform supported by both Haskell and unixODBC.

This driver is the preferred method of communicating with MySQL from Haskell.

MYSQL NOTE

Important note for MySQL users:

Unless you are going to use InnoDB tables, you are strongly encouraged to set

Option = 262144

in your odbc.ini (for Unix users), or to disable transaction support in your DSN setup for Windows users.

If you fail to do this, the MySQL ODBC driver will incorrectly state that it
supports transactions. dbTransactionSupport will incorrectly return True. commit and rollback will then silently fail. This is certainly /NOT/ what you want. It is a bug (or misfeature) in the MySQL driver, not in HDBC.

You should ignore this advice if you are using InnoDB tables.

Skeleton Engine for MySQL is a full framework to plug in a new storage engine. Comes with prebuild autoconf files, and a full framework to plug in your own design.

The AWS, HTTP, Memcache, Nitro, PBXT, and many other engines were put together from the skeleton engine.

To install, grab a copy of the mysql source code and run this:
./configure --with-mysql=/home/brian/mysql-5.1/ --libdir=/usr/local/lib/mysql/
make install

And then inside of MySQL:

mysql> INSTALL PLUGIN skeleton SONAME libskeleton_engine.so;

mysql> CREATE TABLE `d` (`a` varchar(125), b text, primary key(a)) ENGINE=skeleton DEFAULT
CHARSET=latin1;
Query OK, 0 rows affected (0.01 sec)

You will probably need to edit the Makefile.am in the src/ tree if you want to build on anything other then Linux (and the Makefile assumes that the server was not compiled for debug).

mod_dbd_mysql is a DBD Driver module for MySQL. To replace mod_mysql_pool
Main features:
- Dynamic connection pooling for scalable applications.
- Persistent Connection for non-threaded MPMs and legacy applications.
- Single-use connections for debugging or low-usage applications.
- Database-independent framework with driver (DBD) modules for different databases.
- SQL namespace module for direct database access in HTML or XML pages with mod_publisher or mod_xmlns.
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.

guile-dbd-mysql project is a MySQL database driver for the Guile DBI system.
guile-dbi is a database generic interface. Provide a way to use dbds (data base drivers) which are linked at run-time (like perl dbi or php or...) for query different database engines always in the same way.
Enhancements:
- The API has been upgraded to Guile 1.8.

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.

Clevo Mail LED Linux Driver operates the mail LED on the Clevo notebook model D4J.
Enhancements:
- The DMI_BOARD_VENDOR string has been corrected for D410V autodetection.