Open
Description
This should resolve #592. I opted for a separate issue in order to allow for a more focused discourse about this specific approach.
We have a concept for how to load arbitrary aggregates with a single select statement, at least for those databases that support a sufficient subset of the SQL standard.
This ticket is an epic for tracking the progress in the implementation this concept.
Subtickets:
- Support Projections for Single Query Loading on an API level #1579
- Use Single Query Loading for query methods #1658
- Load aggregates that have a single one-to-m relationship with a single select #1446
- Split Single Query Conversion into two-step process #1586
- Load aggregates with a single select in R2DBC. #1447
- Load aggregates that have more than one one-to-m relationship with a single select. #1448
- Load aggregates that have embedded entities with a single select. #1449
- Load aggregates that have one-to-one relationships with a single select. #1450
- Load aggregates that have nested one-to-m relationships with a single select. #1451
- Support Single Query Loading for template methods with arbitrary where clauses #1601
- Support Single Query Loading for template methods with Sort #1545
- Support Single Query Loading for template methods with Pageable #1546