I should note one more thing: this is for *versioned* data only! Otherwise we have no way to relate an instance to its snapshot after deserialization.
> Heh, I was going to post about this. > > I'm not sure whether this is good or bad but I added it for feedback. > > Its a performance optimization: > > Usually when we do session.update(foo), we don't have a snapshot of foo's > clean state. This new feature gives us a memory sensitve cache of > snapshots or "recent" objects. In the case where a snapshot _is_ available > in the cache, we might be able to optimize away the update, or at least > use dynamic-update if that is enabled. > > Note that the reason for this is that objects can't carry around snapshots > the way collections do. > >> Saw subject in the commit logs...What is that ? ;) >> >> /max >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> hibernate-devel mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/hibernate-devel >> > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > hibernate-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
