Free database modeling tools software for linux

Database Fishing Tool is short DaFT is a front-end to any database that can be connected to with an ODBC driver. DaFT allows you to browse the database objects, view data in tables and views, and create and execute SQL statements, also as a script, including variable scanning.
DaFT contains a database objects list (tables and views), list of columns and column properties, a table for data snapshots, detailed data view, a notepad, a table for viewing the outcome of select statements, T-SQL or PL/SQL statements, a SQL statement editor with syntax highlighting, and a screen to follow all ODBC driver messages (errors etc.).
All selected data can be saved into a file. The supported file formats are HTML, XLS, CSV, SyLK, and DIF. The SQL statements can be saved into a text file.
Enhancements:
- Handle Tables, Views, and colums with names (partly) in capitals with surrounding quotes.
- Some bug fixes...

Generator is an command line application written in java that have the goal to make easy the construction of little applications that needs some database objects stuff.
Database Bean Generator isnt a replacement of complex object persistence solutions, like hibernate or TopLink but it covers a different target. The little java web applications that dont use sofisticated persistence options.
Generator invocation is simple, just type:
java -jar generator.jar -xml (config-file.xml)
where config-file is a xml config file with the definitions to connect to the database and generate the bean classes.
Main features:
- Generates classes to access via custom connection resources to database tables.
- Configuration files are in clear xml format and can be embedded or separate.
- Supports individual or global field updates.
- Supports custom set of Exceptions.
- Provides toXML function for each entity generated.
- Provides automatic generation of finders coonfigured in the xml configuration file.
- Provides some utility static methods via the BdUtils.java class generation.
- Generates an xml file with the database structure.
- Supports configuration of the methods that produces XML (String as CDATA, data as attributes or values, ...)
- Initial support for MySQL and Oracle (Oracle support is in initial stage at this moment).
- Provides an ant task for automatic integration builds.
- Supports transparent renaming of the generated class individual fields.
- Supports normal or CDATA output in individual fields.
- Supports utilization in all database methods with your own external connection.
- Preliminar support of a pluggable logging system (The goal is use log4j integration)
- Support for SEQUENCES in Oracle and AUTOINCREMENT in MySQL
- Support arbitrary raw code and imports from configuration file
- Correct treatment for NULL values of the fields in the generated class
Enhancements:
- Optionally, you may include the extra jars to get JSON support.
- JSON output for finders and generic JSON output for general have been added.

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.

Yukatan data model project is the schema definition of the Yukatan webmail database.
The PostgreSQL database structures defined in this file can be used as a backend store of an email message handling application. The database should be created with the "UNICODE" encoding to properly support messages in different languages.
New data types
The special data types commonly used in the Yukatan data model have been made explicit by the introduction of seven new domains. The domains and the related COMMENT statements make field semantics more clear than before.
See the SQL schema file for more detailed documentation on these domains.
Explicitly named constraints
All the table constraints in the database are now explicitly named and documented. This change makes the database implementation more orthogonal and cleans up the documentation.
Renamed fields and tables
All the *address field names have been truncated to *addr, to make it visually clearer that they are always paired with the corresponding *name fields. The change also makes parts of the documentation less repetitive.
The referencesfield table has been renamed to referencefield to avoid the plural form in the table name. Also all the contained references* field names have been renamed to reference*.
Semantic changes
Quite a few changes have been made to the semantics of various fields. The unnecessarily tight constraints on sequence numbers have been replaced with clearer documentation, the format and encoding of most fields has been explicitly documented, and the previously allowed dual use of the enttext and enddata fields has been prohibited.
Dropped envelope data
The envelope data added in version 0.5 of the data model has for now been removed. The reason for the removal is that the envelope data is not an integral part of an email message, and I wanted to make the version 1.0 as clear as possible. The database now stores "email messages" - nothing less, nothing more. Envelope data can and probably will be reintroduced in an incremental version 1.x along with other extensions.
Enhancements:
- cleans up and documents the data model that has developed since version 0.1
- removal of the envelope data added in version 0.5
- enaming and redefinition of some of the fields and tables
- database structure has also been extensively documented

XML::DB::Database::Exist is a Perl module with XML:DB driver for the eXist database.

SYNOPSIS

use XML::DB::Database::Exist;

This is the eXist XML-RPC driver. It is intended to be used through the XML:DB API, so that it is never called directly from user code. It implements the internal API defined in XML::DB::Database

The methods required to implement the Database interface are documented in Database.pm; only methods unique to eXist, and not required by the XML:DB API are documented here.

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.

Media Database is a media database that uses PHP for the GUI and MySQL for data storage.

It has movie, series, and anime listings. Media Database has lending and wishlist capabilities.

Installation:

Unpack mediadb-*.tar.gz to www dir or public_html dir.
Edit config.php, change mysql_user_name, mysql_password and mysql_server_host to match your MySQL database username, password and host.
run url: http://url_to_mediadatabase/install_mediadb.php, and follow the link and log in as admin and make default yourself a user.

*******************************************************************
****** Dont use the admin user for adding films and stuff. ******
*******************************************************************

If there are any problems, please send a short description of where it occurs and the error message to my email addres: marco (at) cakebox (dot) net, marc the topic with [mediadb]: (something you find fitting)