I have entities where batch loading helps in some use cases but it loads
lots of unneeded entities/collections in other complex use cases, where I
have many proxies but only use a few.
My current workaround is doing "manual batch loading" (i.e. dummy query) in
the cases where I need it.
It would be definitely a low-priority but nice-to-have feature.
Diego
On Wed, Sep 1, 2010 at 10:12, Fabio Maulo <[email protected]> wrote:
> It is possible for batcher (INSERT, UPDATE,DELETE).
> I don't understand where it is useful for collection/relations batch-size.
>
>
> On Wed, Sep 1, 2010 at 9:37 AM, Diego Mijelshon <[email protected]>wrote:
>
>> Being able to override batch-size would be useful. Implementing it
>> requires messing with more than one part of the infrastructure, though.
>>
>> Diego
>>
>>