On Feb 27, 2011, at 5:42 PM, Anjo Krank wrote:
> Am 27.02.2011 um 23:18 schrieb David Avendasora:
>
>> Which is why I said "a ticket to patch", as I would be providing a patch,
>> and I showed the code I would be submitting.
>
> This doesn't fix anything. On the next refresh you still won't se
Am 27.02.2011 um 23:18 schrieb David Avendasora:
> Which is why I said "a ticket to patch", as I would be providing a patch, and
> I showed the code I would be submitting.
This doesn't fix anything. On the next refresh you still won't see your
objects, so it will be more confusing, not less.
On Feb 27, 2011, at 11:59 AM, Anjo Krank wrote:
> The batching DG has very different semantics than the non-batching one.
> Basically, all of the EC changing stuff won't work as planned. You can safely
> only use it for querying large data sets.
>
> You should only add a ticket if you also prov
The batching DG has very different semantics than the non-batching one.
Basically, all of the EC changing stuff won't work as planned. You can safely
only use it for querying large data sets.
You should only add a ticket if you also provide a fix, which I estimate is
very hard to do correctly.
Hi All,
Is there a reason why the ERXBatchingDisplayGroup wouldn't increment the
_rowCount variable when you call insertObjectAtIndex?
If you have a BDG that has a rowCount() that is an exact multiple (including 0)
of the numberOfObjectsPerBatch() and you insert a new object, the rowCount()
do
