Free database backend software for linux

MP3-Database project is a tool to organize your MP3 collection. If you insert a CD with MP3 files in your CDROM drive, MP3DB can read all ID3 tags of the MP3 files.
With this information MP3DB creates a database which can be searched for a specific song, artist, or CD.
A GUI makes it easy to use the program. Any title found in the database can easily be added to a playlist or can instantly be played by XMMS.
Main features:
- MySQL (Is needed as database backend)
- Perl5
- Perl Modules:
- Tk
- Tk-MesgBox
- Tk-LabFrame
- Tk-Pane
- DBI
- MP3-Info
- Msql-Mysql-modules
- To play MP3 files the MP3 player XMMS should be installed on your system. MP3-Database can easily be adapted to other MP3 players
Enhancements:
- NEW Data Structure: The MySQL database is much more complex than before. I used 3 Tables for Artists, Albums and Titles to store the data. This ensures that I have no redundancies in the tables. This has also enabled me to store additional fields in the database (for example the date of birth of an artist, or the release year of an album).
- NEW Temporary Database: I added some tables to store all new artists, albums and titles in a temporary database. This enables the user to check the new entries before adding them to the permanent database.
- NEW FEATURES: Additional Artist and Album information can be stored in the database, MP3DB can now create a random playlist and a playlist with the top 20 MP3 titles, MP3DB can show you a statistic how many artists, albums and titles are stored in the database.

PowerDNS Oracle Backend provides a backend which allows PowerDNS to use Oracle as its data store.

PowerDNS Oracle Backend is a backend driver for the PowerDNS nameserver which allows DNS data to be stored in an Oracle database. PowerDNS can load backend modules at runtime. This backend is fully configurable, and SQL statements can be specified in the configuration file.

HP ScanJet 3900 series backend is an application and backend for linux that allows to use HP scanjet series 3900 scanners and, basically, all those controlled by Realtek RTS8822L chipset.
HP ScanJet 3900 series backend application is in early phase of development. Four files are included, two (binary and sources) for the application and two more for SANE backend.
Enhancements:
- Added support for scanner: HP ScanJet G3010 (similar to hp4370)
- Added initial support for scanner: BenQ 5550T (New chipset: RTS8823L-01E).
- Fixed bug related to stepper motor, programming smearing curves for backtracking.
- Implemented algorithm to detect installed RAM type.
- Implemented a better code to read/write in DMA.
- Added some scripts for users, to update, compile and install sources.

HP3300c SANE backend is a Linux SANE backend for the HP3300c USB color scanner.
Support for other scanners with very similar chipsets, like the HP3400c, HP4300c and the Agfa Touch is also planned.
The HP3300C is an USB color scanner. It is externally powered. On the front is has two buttons that can trigger the scanner software to make either a scan or a copy. It has a horizontal resolution of 600 DPI (5300 pixels) and a vertical resolution of 1200 lines per inch.
It has the following chipset:
- NIPEDC0804, two rows of 20 pins along bottom and top edge. It has a 12.000 MHz crystal mounted close to it. This chip was mentioned as an interface chip on an electronics web page. The pinout of this chip is very similar to the Genesys Logic GL640USB chip (datasheet available).
- KM2Q65R, T224162B-28J, 100 Mhz, a 256k x 16 EDO DRAM chip from Taiwan - Memory Technology (TMTech) (datasheet available). The HP3400C has a EliteMT 100 MHz M11B416256A, also a 256k x 16 DRAM chip.
- ESIC ES8100QA, pins on all four sides, the analog-front-end. Also the Wolfson Micro WM8143 (datasheet available) has been reported. These two chips seem to be completely compatible.
- NIASH00014, pins on all four sides, 100 in total. This is the main controller IC. It has a 20.000 MHz crystal on pins 61 and 62. Two HP3400c scanners have been reported to contain a NIASH00019 chip.
Enhancements:
- Added device and company ID for Silitek derivate
- updated testtool_xfer.c

Haskell Database Connectivity project provides an abstraction layer between Haskell programs and SQL relational databases. This lets you write database code once, in Haskell, and have it work with any number of backend SQL databases (MySQL, Oracle, PostgreSQL, ODBC-compliant databases, etc.)
HDBC is modeled loosely on Perls DBI interface http://search.cpan.org/~timb/DBI/DBI.pm, though it has also been influenced by Pythons DB-API v2, JDBC in Java, and HSQL in Haskell.
HDBC is a from-scratch effort. It is not a reimplementation of HSQL, though its purpose is the same.
Main features:
- Ability to use replacable parameters to let one query be executed multiple times (eliminates the need for an escape function)
- Ability to access returned rows by column number
- Ability to read data from the SQL server on-demand rather than reading the entire result set up front
- HUnit testsuite for each backend driver
- Well-defined standard API and easy backend driver implementation
- Lazy reading of the entire result set (think hGetContents, but for the results of SELECT) (see sFetchAllRows)
- Support for translation between Haskell and SQL types
- Support for querying database server properties
- Add-on package (hdbc-missingh) to integrate with MissingH, providing a database backend for AnyDBM.
- Support for querying metadata such as column names.
- Support for querying additional metadata (column types, etc.)

DBPrim project is a library providing basic building blocks for creating in-memory databases.
Main features:
- Linked lists
- Hash tables with optional auto-resize
- Memory-efficient sparse matrices built on hash tables
- Red-black trees.

DITrack is a free, open source, lightweight, distributed issue (bug, defect, ticket) tracking system using a Subversion repository instead of a backend database. DITrack is written in Perl and runs in UNIX environment (*BSD, Linux, MacOS X).
The project is inspired by the idea of Subissue issue tracking system. However, while Subissue aims in merely replacing the traditional database storage with Subversion repository, DITrack is a major rethought of the issue tracking system paradigm.
The main difference is that instead of sticking to the centralized model (one database, one web interface, one mail integration machinery), DITrack treats underlying Subversion storage as a versioned distributed file system which enables benefits of truly distributed operation mode.
Enhancements:
- The major change in this release is the "real" support for disconnected operations.
- There is also a bunch of less significant enhancements (including the installation script) and bugfixes.

Bigtop::Backend::Init::Std is a Bigtop backend which works sort of like h2xs.

SYNOPSIS

If your bigtop file looks like this:
config {
build_dir `/home/yourname`;
app_dir `appsubdir`;
Init Std {}
}
app App::Name {
}

when you type

bigtop --create your.bigtop Init

or

bigtop --create your.bigtop all

this module will generate the build directory as

/home/yourname/appsubdir

Then it will make subdirectories: t, lib, and docs. Then it will make files: Changes, MANIFEST, MANIFEST.SKIP, README, and Build.PL. Finally, it will copy your.bigtop into the docs dir of under appsubdir.

As with any backend, you can include no_gen 1; in its config block:

config {
Init Std { no_gen 1; }
}

Then, no files will be generated. But, you can also exclude indiviual files it would build. Simply list the file name as a keyword and give the value no_gen:

config {
Init Std {
MANIFEST no_gen;
Changes no_gen;
}
}

If you are in create mode and your config does not include app_dir, one will be formed from the app name, in the manner of h2xs. So, in the above example it would be

/home/yourname/App-Name

Outside of create mode, the current directory is used for building, if it looks like a plausible build directory (it has a Build.PL, etc). In that case, having a base_dir and/or app_dir in your config will result in warning(s) that they are being ignored.