Hi List,
well, I need to thank Mark for the advice.
I've used the ERXFetchSpecificationBatchIterator in this way:
@Override
public Object performAction() {
// TODO Auto-generated method stub
EOEditingContext ec = ERXEC.newEditingContext();
EOFetchSpecification fs = new EOFetch
Hi,
I've seen the class!
Now, I'm trying to use it, when I finish the migration, I'll post the
differences!
Thank You
Il giorno gio 10 mar 2016 alle ore 17:13 Mark Wardle ha
scritto:
> Yes. I have just checked and found ERXFetchSpecificationBatchIterator in
> er.extensions.
>
> Mark
>
>
Yes. I have just checked and found ERXFetchSpecificationBatchIterator in
er.extensions.
Mark
> On 10 Mar 2016, at 10:51, Daniele Corti wrote:
>
> Hi,
> I have a question, about performance while working with LongRequest and many
> EO.
>
> Here's the situation: I've prepared a class that exten
I don’t usually fetch all objects but fetch in batches.
You need to recycle the EOEditingContext. I tend to bring the array in batches,
process, then create a new editing context and repeat.
I have some code included below but I think there is also good batching support
in Wonder. The code belo
Hi,
I have a question, about performance while working with LongRequest and
many EO.
Here's the situation: I've prepared a class that extends
ERXLongResponseTask.DefaultImplementation.
In this class, I operate a database migration, over 1 record.
Each of them has, at least, 50/60 objects relea