ObjectiveSync is a thin JDBC object persistence library. If features querying done in SQL, centralized object marshaling and unmarshaling where each object should know how to sync itself and its descendants, a single syntax for inserting and updating, Ruby-like objectivized JDBC fetching with exception handling, user-definable deep fetching and updating (almost Hibernate-like), batch API to avoid round-trips when submitting multiple queries, stats collection, and more.
Caché Monitor is an SQL development tool for InterSystems database Caché. It features an advanced SQL query editor with SQL syntax highlighting, SQL code completion with context sensitive information about database objects (also known as Intellisense), an SQL history buffer for executed SQL commands, SQL code formatting, parallel queries, graphical SQL execution plan with index and selectivity information, SQL abbreviations, and much more. Database diagrams graphically show the structure of the database.
Vibur DBCP is a concurrent, fast, and fully-featured JDBC connection pool based on Java dynamic proxies. It supports a fairness parameter, statement caching, Hibernate integration, and SQL queries logging, among other features. Various configuration examples (with Spring, Hibernate, etc.) are provided.
PGJDBC-NG is an implementation of JDBC for the PostgreSQL server. It aims to support the complete JDBC 4.1. Specifically, it supports the advanced UDT features of JDBC that the mainstream driver lacks. It's implemented using an asynchronous I/O library (Netty), which allows it to support other advanced features like asynchronous notifications.
CsvJdbc is a read-only JDBC driver that uses Comma Separated Value (CSV) files or DBF files as database tables. It is ideal for writing data import programs or analyzing log files. The driver enables you to access a directory or a ZIP file containing CSV or DBF files as if it were a database containing tables. As there is no real database management system behind the scenes, not all JDBC functionality is available.
Midao JDBC simplifies development with Java JDBC. It is flexible, customizable, and simple/intuitive to use, and provides a lot of functionality: transactions, working with metadata, type handling, profiling, input/output processing/converting, pooled datasource libraries support, cached/lazy query execution, named parameters, multiple vendor support out of the box, custom exception handling, and overrides. With a single jar, it supports both JDBC 3.0 (Java 5) and JDBC 4.0 (Java 6). Midao JDBC is well tested. Not only does it have around 700 unit and functional tests, but it's also tested with the latest drivers of Derby, MySQL (MariaDB), PostgreSQL, Microsoft SQL, and Oracle. Midao is a data-centric project. Its goal is to shield Java developer from nuances of vendor implementation and standard boilerplate code. Midao JDBC is the first library released under it.
StelsXML is a JDBC type 4 driver that allows you to perform SQL queries and other JDBC operations on XML files. It allows you to easily access data contained in XML documents using the standard SQL syntax and XPath expressions. The driver is completely platform-independent. It supports most keywords of ANSI SQL'92, XPath expressions for defining tables and columns, inner and outer table joins, aggregate, numeric, string, conversion, and user-defined SQL functions.
StelsCSV is a JDBC driver that allows performing SQL statements and other JDBC operations upon text files (comma separated, tab-separated, fixed length, etc.). Using this driver, users can easily create a simple database consisting of plain text files. The driver can be used for writing data importing programs and migration tools. It supports most keywords of ANSI SQL92, table joins, INSERT, UPDATE, and DELETE statements, data types, aggregate, converting, string, and user-defined SQL functions.
SqliteJdbcNG is a JDBC driver for SQLite. The overall goal of this project is to start a fresh implementation that leverages newly available technologies in the Java world. For example, any SQLite driver for any language must integrate with the native SQLite library. All of the current Java implementations rely on a custom JNI library to call out to the SQLite library. This extra layer can easily create a headache for the development and deployment of the driver, since it needs to be built for a variety of operating systems. Fortunately, there are technologies like Bridj and JNA that can be used to call native code directly from Java. By leaving the majority of the headaches of integrating with the native library to the Bridj project, more time can be spent on making a high quality driver that is more compliant with the JDBC4 spec.