Spring/spring-data-relational
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polishing.

Browse Source 
Delegate BatchJdbcOperations calls to NamedParameterJdbcOperations. Refine since and deprecation tags.

See #1616
This commit is contained in:
Mark Paluch
2023-10-11 09:52:13 +02:00
parent 5d6d575ab2
commit a72bf1a65d
4 changed files with 41 additions and 134 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/main/antora/modules/ROOT/pages/jdbc/entity-persistence.adoc
View File

@@ -30,13 +30,17 @@ This should be significant more efficient, especially for complex aggregates, co
+
Currently, Single Query Loading is restricted in different ways:
1. The aggregate must not have nested collections, this includes `Map`.The plan is to remove this constraint in the future.
1. The aggregate must not have nested collections, this includes `Map`.
The plan is to remove this constraint in the future.
2. The aggregate must not use `AggregateReference` or embedded entities.The plan is to remove this constraint in the future.
2. The aggregate must not use `AggregateReference` or embedded entities.
The plan is to remove this constraint in the future.
3. The database dialect must support it.Of the dialects provided by Spring Data JDBC all but H2 and HSQL support this.H2 and HSQL don't support analytic functions (aka windowing functions).
3. The database dialect must support it.Of the dialects provided by Spring Data JDBC all but H2 and HSQL support this.
H2 and HSQL don't support analytic functions (aka windowing functions).
4. It only works for the find methods in `CrudRepository`, not for derived queries and not for annotated queries.The plan is to remove this constraint in the future.
4. It only works for the find methods in `CrudRepository`, not for derived queries and not for annotated queries.
The plan is to remove this constraint in the future.
5. Single Query Loading needs to be enabled in the `JdbcMappingContext`, by calling `setSingleQueryLoadingEnabled(true)`