Re: [Hibernate-devel] caching algorithm

[Doug C. <de...@fl...>]

> When Loading Objects
> ====================
> 1. grab the current timestamp (before-select)
> 2. issue SQL selects
> 3. hydrate objects
> 4. disassemble hydrated objects
> synchronized {
> 5. check that 'before-select' is greater than 'after-update' for that
> instance
> 6. if so, add the disassembled state to the cache
> }

Hmm. The before-select timestamp is the local time? If the database
uses versioning (or caching) internally, the select could return stuff
as old as the start of the transaction... which could be earlier than
after-update even when before-select isn't.

e