1.1.0-Alpha3

This release includes support for object builders for CTEs and for the returning from modification queries. Implicit joins are now reused and some db2 and mysql fixes have been applied.

1.1.0-Alpha2

This release fixes a cache issue regarding parameter deduplication and includes some performance improvements.

1.1.0-Alpha1

The 1.1.0-Alpha1 release is a mostly stable preview release. Some minor API changes are possible in the next release but the planned features are mostly done.

Changes

• Lot of bug fixes as well as the fix for a memory leak
• Support for multiple from clauses
• Support for CTE queries as part of a main query
• Support for modification queries
• Support for the hibernate insert query
• Support for returning results from modification queries as well as embedding into CTE queries
• Support for limiting queries via the builder API directly
• Support for set operations(union, intersect, except) in normal and CTE queries
• Support for partial entity view updates(minimal features, there will be more in a subsequent Alpha2)

1.0.6

1.0.6 release

Changes:

• Introduced code names that will be printed out on first usage
• Fix for antlr parsing issues
• Allowing custom equals-hashCode for entity views
• Template renderer transitioned to public API for JpqlFunctions
• Implemented support for referencing into embeddables and joining over relations defined in embeddables
• Added datediff functions for major databases
• Initial Datanucleus support
• Support using getter in entity view constructor via unsafe (to disable the usage set unsafe_allowed to false)

1.0.5

1.0.5 release

Important notice:
Versions before 1.0.5 had a concurrency issue in the entity view module. Consider updating!

Breaking changes:

• OrderByBuilderExperimental was removed. The functionality is now usable through the standard orderBy API
  We created the experimental APIs to test out non portable features and we transitioned the functionality into the standard API. If you wish to stay portable, set the property "com.blazebit.persistence.compatible_mode" to true
• JpqlFunction registration was redesigned because aggregate functions wouldn't work as expected
  The migration is to adapt JpqlFunction registrations to the new API which is similar

1.0.4

1.0.4 release

1.0.3

1.0.3 release

1.0.2

1.0.2 release

1.0.1

1.0.0 release

1.0.0

1.0.0 release