-
> From: Joshua Davis [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 03, 2005 10:18 PM
> To: Steve Ebersole
> Cc: Max Andersen; Hibernate development
> Subject: Re: [Hibernate] someone looking at flushing performance...
>
> Steve Ebersole wrote:
>
> >[...snip...
That was not my intent to imply such a thing.
-Original Message-
From: Joshua Davis [mailto:[EMAIL PROTECTED]
Sent: Monday, January 03, 2005 10:18 PM
To: Steve Ebersole
Cc: Max Andersen; Hibernate development
Subject: Re: [Hibernate] someone looking at flushing performance...
Steve Eber
Steve Ebersole wrote:
[...snip...] Then we could continue to track these
objects within the scope of object identity but not in the session cache
(aka, this is analogous to TopLink's distinction between Session and
UnitOfWork).
... except better than TopLink. The TOPLink Session stores objects
Steve Ebersole wrote:
Sure, but all I'm talking about is the processing inside
SessionImpl.flushEntity(). If an entity is not mutable, there is a
bunch of stuff there that is not necessary between wrapping collections
and performing the FlushVisitor processing. The only question would be
the sem
-Original Message-
From: Gavin King [mailto:[EMAIL PROTECTED]
Sent: Monday, January 03, 2005 2:44 PM
To: Steve Ebersole
Cc: Max Andersen; Hibernate development
Subject: Re: [Hibernate] someone looking at flushing performance...
Steve Ebersole wrote:
>The read-only stuff would not
Steve Ebersole wrote:
The read-only stuff would not fix this issue, as I understand it. From
what I think that user is asking for, he still probably wants to the
flushes against the "main entity" to be honored and just wants the
reference data excluded from the flush checking.
I think he's suggest
Sorry for the late reply, I've been out for the holidays and
simultaneously rebuilding my system from its hard-drive crash.
The read-only stuff would not fix this issue, as I understand it. From
what I think that user is asking for, he still probably wants to the
flushes against the "main entity"
