Quoting is important since it allows use of keywords as names.
We do not change the letter casing.
In a default setup the database does not care since it is case-insensitive.
If configured to be case-sensitive it makes sense to pass on what ever letter casing there is, since you seem to care.
Closes#1216
See #914
Delete operations that receive a version attribute throw an `OptimisticFailureException` when they delete zero rows.
Otherwise, the NOOP delete gets silently ignored.
Note that save operations that are determined to be an update because the aggregate is not new will still throw an `IncorrectUpdateSemanticsDataAccessException` if they fail to update any row.
This is somewhat asymmetric to the delete-behaviour.
But with a delete the intended result is achieved: the aggregate is gone from the database.
For save operations the intended result is not achieved, hence the exception.
Closes#1313
Original pull request: #1314.
See https://github.com/spring-projects/spring-data-commons/issues/2651
+ Copy logic from QueryMapper#convertToJdbcValue to resolve Iterable
arguments on findBy* query methods to resolve the same for @Query.
+ Use parameter ResolvableType instead of Class to retain generics info.
Original pull request #1226Closes#1212
Changed default behaviour to an empty name for embedded entities.
This allows to use embedded entities for column tuples without special prefix.
Original pull request #1149
Table alias for embedded entity use prefix value from Embedded annotation. But default value for prefix is empty string. If try to create SqlIdentifier for empty string it throw exception. To avoid this behavior, if prefix is an empty string, property name for embedded entity is taken instead.
This change extracts entity modifying behaviour into separate methods, so it doesn't appear as an unexpected side effect of the creation of aggregate changes.
Also some formatting.
Original pull request #1196
See #1137
Insert for entities of same type within an aggregate get inserted using JDBC batch operations when possible.
Inserts are supported when no id needs to be generated by the database or if the Dialect supports generation of ids in batch operations.
Closes#1159
Original pull request # 1191
Added the missing functionality that is found in the documentation of spring-data-jdbc, but was not present in the code as functionality. Users can not choose between various QueryLookupStrategies.
Closes#1043
Original pull request #1187
We now associate a boolean value with both operators as those operators are rendered using equals comparison in the actual SQL text.
Orginal pull request #1188
This allows both Spring Data R2DBC and Spring Data JDBC to use the same annotation.
See spring-projects/spring-data-jdbc/issues/1041, spring-projects/spring-data-r2dbc/pull/720, spring-projects/spring-data-jdbc/pull/1158
Mark Paluch
Jens Schauder
Dmitriy
Spring Builds
Christoph Strobl
Chirag Tailor
Daniil Razorenov
Greg L. Turnquist
Diego Krupitza
Oliver Drotbohm