Free jdbc drivermanager software for linux

JDBC Driver for SQLite is a thin layer on top of the SQLite 3.3.x C API. The native JNI library has SQLite compiled into it so all you need to do is include the two files packaged above in your project.
Usage:
Download the binary for the platform you are developing on. Open the tarball and copy the two files into your application directory:
sqlitejdbc.jar
[lib]sqlitejdbc.[dll, so, jnilib]
Reference the driver in your code:
Class.forName("org.sqlite.JDBC");
Connection conn = DriverManager.getConnection("jdbc:sqlite:filename");
// ... use the database ...
conn.close();
And call your program with the drivers JAR file in the classpath and the C library in the librarypath. E.g.
java -cp lib/yourprog.jar:lib/sqlitejdbc.jar
-Djava.library.path=lib
yourprog.Main
Enhancements:
- The driver is now thread-safe and fully supports UTF-16.
- There are binaries for Mac OS, Linux, and Windows, and instructions for compiling with MSVC.

SchemaCrawler project is a command-line tool to output your database schema and data in a readable form.
The output is designed to be diff-ed with previous versions of your database schema. SchemaCrawler is also an API that improves on the standard JDBC metadata.
Enhancements:
- SchemaCrawler now comes with bundled downloads for Microsoft SQL Server and MySQL.

Schema Crawler project is a platform (database and OS) independent command-line tool to output your database schema and data in a readable form.
The output is designed to be diff-ed with previous versions of your database schema. Schema Crawler is also an API that improves on standard JDBC metadata.
Build
Ant Build
The ant build is a quick build that builds the Schema Crawler jar without compiling and running unit tests. Download ant, and run it from the Schema Crawler directory. The jar file will be created in the _distrib directory. The main targets are all.build and all.clean.
Maven Build
The maven build is a more comprehensive build that runs unit tests, and also creates the project web-site. Download maven, and run it from the Schema Crawler directory. The jar file will be created in the _distrib directory. The main goals are all.build and all.clean.
Eclipse
Schema Crawler consists of two Eclipse projects, dbconnector and schemacrawler. Since schemacrawler depends on dbconnector, you will need to import both projects into Eclipse.
Enhancements:
- Database properties are now retrieved, along with column data types, both system data types, and UDTs.
- A new command, maximum_schema, gives all possible details of the schema, including database system properties.
- Bugs with the merge rows option and with appending output for multiple runs of SchemaCrawler are fixed.
- An SQL exception with the Oracle Database 10g Express Edition driver on outputting views is fixed.

HA-JDBC project is a JDBC driver implementation that provides light-weight, transparent clustering capabilities to groups of homogeneous JDBC- accessed databases.
Main features:
- Supports any database accessible via JDBC.
- High-availability - Database cluster can lose a node without failing the current transaction.
- Improves performance of concurrent read-access by distributing load across individual nodes.
- Support for full JDBC 3.0 (Java 1.4) feature set.
- Compatible with JDBC RowSet implementations found in Java 1.5.
- Out-of-the-box database-independent strategies for synchronizing a failed cluster node.
- Exposes JMX management interface to allow administration of database clusters.
- Open source (LGPL).

JdbcTool project is a collection of command line utilities for making your life easy when working with Java JDBC databases. Included are:

jdbctool:

An interactive command line tool for executing SQL statements.

jdbcdump:

Dump the contents of a database as SQL statements into a file, like mysqldump.

jdbcload

Execute SQL statements from a file (the opposite of jdbcdump)

Currently, only HSQLDB is supported.

JDBCPersistence project is an Object Relational Mapping Framework. Designed for use in high volume online banking application the package delivers performance matching of that exhibited by hand written JDBC code.

The differentiating features of JDBCPersistence are a result of the focus placed first and foremost on performance followed by making programmer most effective by building on existing knowledge of SQL, JDBC APIs, IDEs and, at the same time, avoiding creation of dependencies on specific libraries, tools, IDEs.

The framework strikes a good balance in what it provides verses what it requires a programmer to do in order to use it, e.g. a programmer could quickly prototype value objects by specifying them as Java interfaces and asking the framework to provide implementation for these interfaces at runtime, thus allowing to go from specifying an interface to using it in no time.

On the other hand, recognizing that data relationships are governed by business rules much more complex than could be specified in a typical ORM configuration file, a programmer is required to maintain such relationships in code.

The focus of the framework is to provide ORM services while leaving other concerns, in particular, data caching, up to the developer to solve in the context of an application. Being aware that the caching requirements may be different in online vs. batch application, the framework does not prescribe a solution. Developer needs to decide on application specific caching policy and implement it in an architectural layer (DAO) designed to function in both contexts.

The framework does not add any behavior to the classes that comprise the application. Classes supplied by the developer are the classes that will be used by the application when it runs.

JDBCPersistence uses bytecode generation technique to create bytecode for classes that implement logic used for persisting the data. Such, for every, loosely speaking "Java Bean", that requires persistence, a persistor class that implements CRUD operations is created. As opposed to using reflection, the approach of generating bytecode is apt to further optimization by JVM.

JDBCPersistence takes bytecode generation a little further by providing a feature that allows generating complete implementation of a value object specified as an abstract class. Similar to generating full implementation for Java interface class that describes value object class, the framework can generate implementation for all abstract methods of an abstract class representing value object.

As all of the bytecode generation takes place at run time, there is no impact on development or build process. The approach of generating bytecode at runtime is also used by RMI implementation of the Java Platform starting with version 5.0.

The API of the framework builds on the existing JDBC APIs. JDBCPersistences public API adds four classes and three interfaces. As the framework uses SQL for queering the data a curve associated with learning framework specific query language is avoided.

In an attempt to "keep it simple" JDBCPersistence only dependency is ASM, which is used for bytecode generation. The footprint of the package is under 200K.

SQLiteJDBC is a JDBC driver for SQLite which is written as a Java JNI layer over the SQLite 3.3.x API.

SQLiteJDBC supports the most commonly used features of JDBC that can be efficiently implemented on top of SQLite. Only a single native JNI library is required, and SQLite is compiled in.

Binaries are provided for Linux, Mac OS X, and Windows.

Home Media Librarian provides an application to catalog records, CDs, DVDs, etc.

HML is a pure Java client(GUI) application to catalog records, cds, dvds, etc.
HML requires a JDBC compliant database and driver.

The application is for the average person whom has a record, cd, dvd, tape, etc. music collection and wants to catalog this collection.

It has been tested with JDK 1.3 and 1.4 on Macintosh OSX, Linux, and Windows 2000 using MySQL and Connector J.

The distribution includes the software,documentation, and source code.