Free database visio modeling tool 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...

MP3DB2 is a collection of bash scripts for keeping track of large MP3 collections. It will retrieve song information from the filenames and ID3 tags of a directory or CD of MP3s and store them in a local database.
This program is a complete rewrite of my MP3 database version 1. Version 1 only stored the data that was present in the filenames while version 2 actually retrieves information from the ID3 tags of each MP3.
Please note that as of this version the database format is NOT considered carved in stone. I have already added a few fields mid-development and this will continue for a while if I think the format can be made better. See the changelog for a list of changes to the database format since V2.0.
Enhancements:
- mp3dupe: now just displays the name of the directory we are checking not the full path in the host filesystem.

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.

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

H2 Database Engine is a free SQL database engine writen in Java.
JDBC and ODBC APIs are supported. Embedded and server modes are available. A Web console application is included. Clustering is supported.H2 Database Engine is a web based java database engine.
Main features:
Fast database engine
- Free, source code is included
- Supports standard SQL
- Written in Java
- Disk based or in-memory databases
- Browser base Console application
- JDBC API
- Limited ODBC support
- Embedded and client/server (network) mode
- High availablility support (clustering / failover)
- Wide range of data types including large objects (BLOB/CLOB)
- Strong security features (SSL, users, roles, encrypted files)
- Multiple connections, table level locking
- Cost based optimizer, using a genetic algorithm for complex queries
- Transaction support (serializable transaction isolation)
- Zero-administration, automatic recovery
- Large resultset, external sorting
- Scrollable and updatable resultset support
- Read only views and inline views
- Inner and outer joins, subqueries
- Many functions already built-in
- Triggers and Java functions / stored procedures
- Referential integrity / foreign key constraints with cascade, check constraints
- Multiple schema support
- Compatibility modes for HSQLDB, MySQL and PostgreSQL
- Sequence and autoincrement columns
- Well tested (high code coverage, randomized stress tests)
- Small footprint (smaller than 1 MB)
- Uses a small number of database files
- Can be compiled to native code using GCJ
- Primary keys, multiple index types (b-tree, linear hash, tree, hash)
- ORDER BY, GROUP BY, HAVING, UNION, LIMIT
- Information Schema
- Multiple connections
- Collation support
- EXPLAIN PLAN support
- The database can generate SQL script files
- Support for linked tables, and a built-in virtual range table
- Automatic re-compilation of prepared statements
- Sophisticated trace options
- Low memory requirements
- Easy to understand exception messages
- Standard handling of NULL values
- Multilanguage console application (at this time, English and German)
Currently, this is not traditional GPL software, but the source code is included. It is free for private and commercial use.
Enhancements:
- H2 now supports the PostgreSQL network protocol, and can be accessed using the PostgreSQL ODBC driver.
- Regular expressions are now supported.
- The per session undo log and referential integrity can be disabled.
- Default settings have been changed to save memory. NOT, boolean columns, and certain joins are optimized now.
- Part of the documentation has been translated to Japanese.

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.

GNUstep Database Library 2 (GDL2) is a set of libraries to map Objective-C objects to rows of relational database management systems (RDBMS).
GNUstep Database Library 2 aims to be compatible with Enterprise Objects Framework (EOF) as released with WebObjects 4.5 from Apple Inc.
Main features:
- EOControl (gnustep-db2control)
- The fundamental abstraction library which includes many non RDBMS related extensions such as KeyValueCoding extensions and other categories. Most importantly it contains the classes which handle the coordination of object graphs namely EOEditingContext.
- EOAccess (gnustep-db2)
- This library implements the underlying mechanism to retrieve and store data in RDBMS. It defines the abstract classes like EOAdaptor which are subclassed to interface with concrete RDBMS implementations.
- EOInterface
- This library implements classes used to synchronize UI components such as NSTextFields, NSButtons and NSTableViews with the state of objects which an EOEditingContext contains.
- EOAdaptors
- This is a collection of concrete EOAdaptor projects needed to connect to specific databases. GDL2 currently only supplies an Adaptor for the PostgreSQL database. Even though the Adaptor is still called Postgres95 we aim to support PostgreSQL 7.2 and higher API. In fact the Adaptor may very soon be renamed to PostgreSQL.
- DBModeler