nf1db is an in memory database engine with SQL and JDBC interfaces. It supports transactions, commands from the SQL-2003 standard, all major data types, a number of functions, default and null values, auto-increments, constraints, primary and foreign keys, set operations, implicit and explicit joins, nested SELECT statements, quantity limits in SELECT statements, and much more.
Awake SQL is a virtual JDBC Driver and a framework that enables remote JDBC access through HTTP. It allows Android and Java desktop app developers to use regular JDBC calls to access remote SQL databases in the cloud. It implements the main data types including blobs/clobs, and supports transactions. Security has been taken into account from the design stage: server-side configuration lets admins specify strong authentication and security rules in order to protect the databases.
The RepairsLab system allows you to manage the entry and exit of equipment repair in a small workshop for repairs or service center. The application allows the printing of a "Repairs sheet" for each device and manages the state of repair. Inside the Repairs ticket, you can enter the features of the delivered and the state of repair. The system provides management of different master data for definition of states of repair, customers, types of equipment, trademarks, and models. You can print a paper "Repairs sheet" in duplicate to store paper and as a delivery receipt for the customer.
SpiderDB is a lightweight database schema crawler library developed using Java. It is a simple library that can be used to Crawler the underlying schema of a database and return POJO objects, which makes it very easy to use. This library takes care of all the differences among the various database management systems, and makes application code free from the DBMS differences.You keep using same POJOs even if you change the underlying DBMS.
persistence4j is a small and lightweight Java object persister that uses JDBC to persist data into a relational database. The library frees you from writing the Data transfer objects - just create a POJO and simply save it. Transactional and non-transactional connections are supported and can be configured from the simple properties file.