ok, the difference in eager/evict policies you say is good enough a
reason to throw my patch to garbage;
I'll fix it for the 80% case, hoping people uses session.clear and not
session.evict to manage memory.
thanks,
Sanne
2009/1/14 Emmanuel Bernard :
>
> On Jan 13, 2009, at 18:35, Sanne Grinover
On Jan 13, 2009, at 18:35, Sanne Grinovero wrote:
thank you, you helped me a lot; still I would like to propose an
evolution to cover all use cases correctly.
I've already implemented and tested this, in roughly three steps:
1)
when moving the cursor outside of the loaded window boundaries I
thank you, you helped me a lot; still I would like to propose an
evolution to cover all use cases correctly.
I've already implemented and tested this, in roughly three steps:
1)
when moving the cursor outside of the loaded window boundaries I
extract the new EntityInfos from the index, then verify
Clearly we cannot solve all use cases, so let's focus on the most
useful one.
People use scrollable resultset to walk through all objects in a
window one after the other wo skipping them.
while( rs.hasNext() ) {
Address a = (Address) rs.get(0)[0];
doSomething(a);
if (i++ % 100 == 0) s.c
