We now use explicitly named selection items when selecting items from a projection selection to avoid name clashes through implicit naming.
Signed-off-by: oualid.bouh <oualid.bouh@kleegroup.com>
Closes#4135
Original pull request: #4136
All findAll methods now require a non null except one.
Changing it to non-null would have been a breaking change since the implemented interface defines the Specificaton as nullable.
Closes#4131
Original pull request #4132
Remove unnecessary comma after 'both' in the sentence structure
'both A and B'. The comma between 'both' and the first item is
grammatically incorrect.
Original pull request #4122
Signed-off-by: Byungju Ju <wnqudwnrlrl@naver.com>
The title for Example 11 was updated to include '@NativeQuery', as the code snippet
demonstrates QueryRewriter usage with both @Query and @NativeQuery. The title for
Example 7 was similarly adjusted to use '@NativeQuery'.
Original pull request: #4120
Signed-off-by: Yohan Park <88149844+yohan9569@users.noreply.github.com>
Enable EclipseLink integration tests for UserRepositoryTests. Disable tests that fail because of non-spec compliance, update test to pass structured query parsing.
Improve exception message for failures if the CriteriaBuilder does not support ILIKE.
Move tests to according test classes.
See #4112
Simplify AotQuery design, introduce isDerived() flag and NamedQuery (including isManaged flag) to improve encapsulation and simplify the flow.
See #4102
We now correctly obtain a list of entities to be deleted and remove those through EntityManager.remove(…). Previously, we've erroneously used executeUpdate(…) that is intended for string-based queries only.
Closes#4102
We now properly consider results of GROUP BY count queries returning potentially multiple rows, a count for each group instead of enforcing a single result item.
Closes#4096
Next to explicitly disabling query checks during AOT we now use an internal Dialect serving for required JdbcSettings.DIALECT. The name of the dialect is printed on info level via the JdbcEnvironment. Providing a meaningful name helps users understand better what is going on.
See: #4068
We now consider the full join path in JpqlQueryBuilder to fix the cache key used to capture joins. Previously, we only considered the property name (a single property path segment) causing omission of joins using the same property name.
Closes#3989
Mark Paluch
Tran Ngoc Nhan
Christoph Strobl
oualid.bouh
Jens Schauder
Byungju Ju
Yohan Park
Oliver Drotbohm