Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Do Hibernate cache concurrency strategies apply to its query cache too (e.g. a cacheable query gets some scalar data, and then two queries concurrently modify that scalar data)? If not, what happens with concurrent updates (or read/updates) for queries? If yes, how to specify them for query cache?
The strategy is the following.
A timestamp cache keeps track of the last update timestamp for each table.
Each time a cachable query is executed and that the results are in the query cache, Hibernate checks the the timestamp of the query results is bigger (more recent) than the update timestamp of each table concerned by the query. If bigger, then the results are not stale, and the cached results are returned. If lower, then the cached results are potentially stale, and the query is executed against the database.