1.8

• Immutable entities

Since this moment Entities are immutable. As a result of every object chang (by settter), a new instance is being created. Immutable objects may be easy cloned by the reference duplication. Because of that, Daobab Entities are fully tread-safe.

• Frozen queries

Every query (Daobab object) may be 'frozen'. After this operation, the query cannot be modified (until unfreeze).
Frozen queries are extremely quick. Like a regural native queries.
This kind of queries however, still accepts dynamic parameters (like JPA Repository does).
Daobab "native" queries, so those where you provides the sql, are also frozed from now. It's possible to use parameters on them as well.

• ultra-fast Json convertion

really fast internal Json conversion. Daobab uses the information he has about the field types to make the json conversion very efficient.

• Internal TypeConverters

responsible for conversion from database object to any Java type

• Introduced REPLACE INTO

insert but on duplicated records only

• Introduced on duplicated key update

actions when rows are duplicated

• Insert for selected columns only

• removed countAny and distinct methods from query objects

those operations are available as regural functions from now on

• entities must have two contructors

Daobab revers engeenering creaed entities having double constructors. It speed up the internal immutable object creation.

• Introduced ColumnCache - column interfaces are simplified and optimized

• EntityRelation interface renamed to RelatedTo

• massive internal refactoring and cleaning