Re: [Hibernate-devel] caching algorithm

[Gavin_King/Cirrus%<CI...@ci...>]

> 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.


aaahhhh of course. interesting. So we should use a timestamp from before
the start of the session?

PS i should have mentioned two cases where we _know_ this algorithm breaks

1. using JTA.
2. non-exclusive access to database

any *other* problems?