Improve performance of results with relationships [DATAJDBC-368]

[spring-projects-issues]

altancabal opened DATAJDBC-368 and commented

When the returned element is an entity with relationships like the LegoSet aggregate example in the [Spring Data JDBC basics repository|https://github.com/spring-projects/spring-data-examples/tree/7b0c7a539b4d02ce6e214978f5e113c959a50f8f/jdbc/basics], then a query is executed for every element in the result.

For example, if you add repository.findAll(); at the end of the customQueries() aggregation test, after the first query is executed, an additional query is executed for every model in the result. This is very time consuming.

 
 

---

No further details from DATAJDBC-368

[benzen]

In this it's unclear what Test is described.

I'd like to contribute at least with a failing test here.

[schauder]

Your willingness to help is appreciated. But in this case it is actually not going to be helpful. We are working on a big change which will come with plenty of tests, so a separate test wouldn't really help.

[codering]

We are working on a more efficient way to load aggregates.

Is there any update now？

[mipo256]

As mentioned in this issue #1434, we should also consider the ability for the use r to configure the strategy of fetching aggregate along with its children - second SELECT or JOIN

[schauder]

Duplicate of #1445