During the development of 6.x, support for {{BatchFetchStrategy}} as applied to {{@BatchSize}} for entity and collection fetches was not ported due to time constraints.
In the interim, {{BatchFetchStrategy}} was deprecated. Which is fine. I think the strategy for entity and collection batch fetching should be a mix {{DYNAMIC}} and {{PADDED}}, based on the outcome of the underlying {{Dialect#getDefaultBatchLoadSizingStrategy}}
The current implementation implements the {{DYNAMIC}} strategy .
Implement support for When {{PADDED}} is used, we should cache the generated SQL AST . When {{ LEGACY DYNAMIC }} ? , we should maybe offer some limited caching of SQL AST(s). |
|
