v0.9.50

1. Fix #908, #912, #915
2. Provide #900, #910, #914

v0.9.49(Big Change)

1. Support join fetch for reference association (one-to-one or many-to-one), and property-level configurations are supported by Output DTO.

   Development has been finished now, so documentation is not ready, short guide here

   • Java Fetcher Example:

     https://github.com/babyfish-ct/jimmer/blob/main/project/jimmer-sql/src/test/java/org/babyfish/jimmer/sql/fetcher/JoinFetchTest.java

   • Kotlin Fetcher Example:

     https://github.com/babyfish-ct/jimmer/blob/main/project/jimmer-sql-kotlin/src/test/kotlin/org/babyfish/jimmer/sql/kt/query/JoinFetchTest.kt

   • Java OutputDTO Example:

     • UserView2 in https://github.com/babyfish-ct/jimmer/blob/main/project/jimmer-sql/src/test/dto/User.dto

     • BookViewWithConfiguration and BookViewWithConfiguration2 in https://github.com/babyfish-ct/jimmer/blob/main/project/jimmer-sql/src/test/dto/org/babyfish/jimmer/sql/model/Book.dto

   • Kotlin OutputDTO Example

     • UserView2 in https://github.com/babyfish-ct/jimmer/blob/main/project/jimmer-sql-kotlin/src/test/dto/User.dto

     • BookViewWithConfiguration and BookViewWithConfiguration2 in https://github.com/babyfish-ct/jimmer/blob/main/project/jimmer-sql-kotlin/src/test/dto/org/babyfish/jimmer/sql/kt/model/classic/book/Book.dto

   9 built-in configurations: !fetchType, !where, !orderBy, !filter, !recursion, !limit, !offset, !batch, !depth

   The Antlr grammar for the AST of newest OutputDTO: https://github.com/babyfish-ct/jimmer/blob/main/project/jimmer-dto-compiler/src/main/antlr/org/babyfish/jimmer/dto/compiler/Dto.g4

2. Global configuration jimmer.mutation-transaction-required, if it is true, any mutation operations without transaction context will report error.

v0.9.47

#884, #885., #886. #887

v0.9.46-Big Change

1. Big enhancement, merging conflict table joins becomes smarter

   For conflict table joins with different join type (INNER, LEFT, RIGHT, FULL)

   Conflict table joins with same join type will always be merged

   • If join paths are declared in and predicate, they will be merged

     

     And predicate support simpler code style, not only where(and(a, b)) is OK, but also more styles such as where(a) where(b), where(a, b)

   • If join paths are declared in or predicate, they will not be merged

     

   Mechanism: There is a class called JoinTypeMergeScope, the default scope is null (Global default scope), the or predicate creates separated merge scope for each sub predicate, only the join paths in same merge scope can be merged.

   Note, if the function or has only one non-null (dynamic predicate such as "table.name eq? sth" may return null) sub predicate argument, this function will be optimized, no or predicate will be created and the argument will be returned directly so that no merge scope will be created.

2. FR #878 is supported.

v0.9.45

1. Enhance UpsertMask
2. #874, #875, #876

v0.9.44

• Provided #869

• Fixed #872

v0.9.43

Fixed #870

v0.9.42

• Fixed #868
• Fixed second problem of #864

v0.9.41

1. Fixed critical bug: #864

2. Fixed other bugs and provide new features: #850, #854, #860, #862 (SQLite)

v0.9.37

Fixed #849