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

v0.9.36

Fix bug #847 and merge PR #848 to resolve crtical bugs after big refactor for MySQU issues

v0.9.35

• #839, #842, #843, #844, #845

• Add setMaxCommandCount for save command and delete command

v0.9.32

1. Improve save-command, remove unnecessary query during error investigation
2. Less limitation for @LogicalDeleted, if the property type is int or enum, the property can be decorated by @Default
3. More limitation for @LogicalDeleted of kotlin, if property type is boolean, int or enum, it cannot be nullable