Considering the time spent doing the iteration (according to your
results) I think it's quite safe to say that any calculation or work
you're going to do will make that time insignificant. Accordingly, I'm
in favor of changing the behavior as proposed.
Cheers,
Frederik
On 16/02/2009, Tobias Schli
Hi,
On 02/16/2009 02:42 PM Frederik Holljen wrote:
> I vote for making it a parameter when you create the iterator. If
> someone uses this to loop through 100k objects fetching and releasing
> that memory that many times is going to be a considerable amount of
> work. I seem to remember that is th
I vote for making it a parameter when you create the iterator. If
someone uses this to loop through 100k objects fetching and releasing
that memory that many times is going to be a considerable amount of
work. I seem to remember that is the reason why we made it that way.
(if not, why don't you jus
I agree to treat this as a bug, which from an OO perspective it is.
On Mon, 16 Feb 2009 12:01:43 +0100, Tobias Schlitt wrote:
> Hi folks,
>
> during implementation of the identity map pattern for PersistentObject I
> stumbled over a behaviour of ezcPersistentFindIterator, which I did not
> expe
On Mon, 16 Feb 2009, Tobias Schlitt wrote:
> I personally would like to treat the current behavior of
> ezcPersistentFindIterator as a bug and fix it to not overwrite object
> states anymore.
I agree with that.
regards,
Derick
--
Components mailing list
Components@lists.ez.no
http://lists.ez.no
Hi folks,
during implementation of the identity map pattern for PersistentObject I
stumbled over a behaviour of ezcPersistentFindIterator, which I did not
expect:
If you use this iterator implementation to fetch objects iteratively,
object instances are re-used on every iteration step. This means
