Before this fix, whenever a column of an inline query was rendered the `InlineQuery` and all its children were visited, resulting in spurious output.
This is no prevented by injecting a NoopVisitor.
Closes: #1362
Original pull request: #1368
This allows ordering by functions like:
ORDER BY GREATEST(table1.created_at, table2.created_at) ASC
or by arbitrary SQL snippets
orderBy(OrderByField.from(Expressions.just("1")).asc()) => ORDER BY 1 ASC
Original pull request #1348
Do not expose setForeignKeyNaming methods on NamingStrategy to make less assumptions about how a naming strategy gets implemented. Provide getRequiredLeafEntity method on PersistentPropertyPathExtension to reduce null and state assertion checks.
Refine getTableName/getQualifiedTableName approach to reduce API surface and avoid deprecations.
See #1147
Original pull request: #1324.
The new default is to take `@Table` annotations into account.
The behaviour can be configured by setting the `foreignKeyNaming` property on the `RelationalMappingContext`.
Closes#1162
See #1147
Original pull request: #1324.
The default version is the behavior that existed so far:
The back reference is the table name as generated by the `NamingStrategy` without taking `@Table` annotations into account.
The new alternative is to take `@Table` into account.
The behavior can be configured by setting the `foreignKeyNaming` property on the `RelationalMappingContext`.
Closes#1161Closes#1147
Original pull request: #1324.
You may now annotate properties of the aggregate root with `@InsertOnlyProperty`.
Properties annotated in such way will be written to the database only during insert operations, but they will not be updated afterwards.
Closes#637
Original pull request #1327
Use consistent method and argument names for newly introduced methods. Reorder and group template API methods to keep related methods together.
See: #1315
Original pull request: #1324.
Code changes to check for both null and empty criteria before proceeding to where clause generation avoids exception.
Closes#1329
Original pull request #1338
Modifying queries are executed directly against the database.
No events or callbacks get called.
Therefore also fields with auditing annotations do not get updated if they don't get updated in the annotated query.
Closes#970