metolithe

A minimal, opinionated, flat key/value JDBC object storage framework.

2.0 Functionality

• No support for composite primary keys (explain why).
• Unique constraints (only two levels supported for now).
• Composite index attributes.
• Static DAO code generation.
• Pagination support.

Documentation topics

• How are primary key fields assigned and extracted.
• Strategies for choosing primary key component fields (or not at all).
• int vs Integer, when to use which?
• How to handle schema migrations with Liquibase generated change sets.
• Always make sure that your schema class names do not clash with database keywords.
• If you do not specify unique constraint tags on your classes, you are responsible for managing each object's primary key values.

Classes which do not define a primary key field can only be saved, loaded or deleted using one of its attributes. Therefore, calls to update or upsert on a DAO instance will fail.

This restriction is by design in this framework.

Resources

• https://blog.jooq.org/faster-sql-paging-with-jooq-using-the-seek-method