Emma is a graphical toolkit for MySQL database developers and administrators.
It provides dialogs to create or modify MySQL databases, tables and
associated indexes. It has a built-in syntax highlighting SQL editor with
table- and fieldname tab-completion and automatic SQL statement formatting.
The results of an executed query are displayed in a resultset where the record-
data can be edited by the user, if the SQL statement allows for it. The SQL
editor and resultset-view are grouped in tabs. Results can be exported to CSV
files. Multiple simultaneously opened MySQL connections are possible.
MySQL Connector/J is a native Java driver that converts JDBC (Java
Database Connectivity) calls into the network protocol used by the
MySQL database. It lets developers working with the Java programming
language easily build programs and applets that interact with MySQL
and connect all corporate data, even in a heterogeneous
environment. MySQL Connector/J is a Type IV JDBC driver and has a
complete JDBC feature set that supports the capabilities of MySQL.
This port is derived from the original databases/mysql-jdbc-mm port of
the mm.mysql JDBC connector by dglo@ssec.wisc.edu.
Class::DBI provides a convenient abstraction layer to a database.
It not only provides a simple database to object mapping layer, but can
be used to implement several higher order database functions (triggers,
referential integrity, cascading delete etc.), at the application level,
rather than at the database.
This is particularly useful when using a database which doesn't support
these (such as MySQL), or when you would like your code to be portable
across multiple databases which might implement these things in
different ways.
DBIx::Abstract - DBI SQL abstraction.
This module provides methods for doing manipulating database tables
This module provides methods retrieving and storing data in SQL
databases. It provides methods for all of the more important SQL
commands (like SELECT, INSERT, REPLACE, UPDATE, DELETE).
It endeavors to produce an interface that will be intuitive to those
already familiar with SQL.
Notable features include:
* data_source generation for some DBD drivers.
* Can check to make sure the connection is not stale and reconnect
if it is.
* Controls statement handles for you.
* Can delay writes.
* Generates complex where clauses from hashes and arrays.
* Shortcuts (convenience functions) for some common cases. (Like
select_all_to_hashref.)
A better alternative to the native transaction signals of Django.
Sometimes you need to fire off an action related to the current database
transaction, but only if the transaction successfully commits. Examples:
a Celery task, an email notification, or a cache invalidation.
Doing this correctly while accounting for savepoints that might be
individually rolled back, closed/dropped connections, and idiosyncrasies of
various databases, is non-trivial. Transaction signals just make it easier
to do it wrong.
django-transaction-hooks does the heavy lifting so you don't have to.
mysqlbackup: create MySQL-database servers backup easy
Why mysqlbackup?
1. Requires minimum coding to create everyday MySQL-backups with some
additional functions.
2. Backups can be compressed on-the-fly and automatically rotated after
specified number of a days past.
3. "Slave mode" feature - stop slave, save it's status and then create backup.
Start slave afterwards.
4. Includes basic database maintenance: check, optimize tables before backup
creation.
5. It can be safely used on a large MySQL installations (1000+ databases).
6. It is written in sh - code interpreter available in a base system.
This is South, intelligent schema migrations for Django apps.
South is:
* Intelligent; it knows if you've missed out a migration or two
* Database independent, so there's no hassle if you need to move databases.
* Easy; it can write migrations for you, and it takes about a minute to
convert your app over to use South.
* Designed for a pluggable Django world; you can declare dependencies
between apps so they all migrate together correctly, and you can still
use syncdb for your non-migrated apps without it interfering.
* Useful for data too; you can write migrations to transform legacy data.
* Better (we think, anyway) than the alternatives.
LMDB is an ultra-fast, ultra-compact key-value data
store developed by Symas for the OpenLDAP Project.
It uses memory-mapped files, so it has the read
performance of a pure in-memory database while still
offering the persistence of standard disk-based
databases, and is only limited to the size of the
virtual address space, (it is not limited to the
size of physical RAM). LMDB was originally called
MDB, but was renamed to avoid confusion with other
software associated with the name MDB.
This distribution provides an API for the GeoIP2 web services and databases. The
API also works with the free GeoLite2 databases.
See GeoIP2::WebService::Client for details on the web service client API and
GeoIP2::Database::Reader for the database API.
cdb is a fast, reliable, lightweight package for creating and reading
constant databases. Its database structure provides several features:
* Fast lookups: A successful lookup in a large database normally takes
just two disk accesses. An unsuccessful lookup takes only one.
* Low overhead: A database uses 2048 bytes, plus 24 bytes per record,
plus the space for keys and data.
* No random limits: cdb can handle any database up to 4 gigabytes. There
are no other restrictions; records don't even have to fit into memory.
Databases are stored in a machine-independent format.
* Fast atomic database replacement: cdbmake can rewrite an entire
database two orders of magnitude faster than other hashing packages.
* Fast database dumps: cdbdump prints the contents of a database in
cdbmake-compatible format.
cdb is designed to be used in mission-critical applications like e-mail.
Database replacement is safe against system crashes. Readers don't have
to pause during a rewrite.
Note for developers: packages that need to read cdb files should
incorporate the necessary portions of the cdb library rather than
relying on an external cdb library. (See WWW)