jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hanson Char <hanson.c...@gmail.com>
Subject Re: JCS Setup Questions
Date Tue, 08 Mar 2005 11:03:04 GMT
> Hibernate makes it easy to cache 
> particularly attractive, which is the query cache.  Hibernate
> saves the last update timestamp of any time a row in any table
> was updated, or an insert or delete performed.  When a query is
> performed and the result set is already cached, the last update
> timestamps are checked behind the scenes for all tables involved
> in the query.  If any of the timestamps are later than the time
> the query is performed, the cached result set is disregarded and
> a new trip to the database is performed.  This is a good thing,
> since now I do not keep track of all queries that may use a
> particular object, and can rely on Hibernate to do this checking
> for me.

+1 

> To implement this myself would be much more difficult.

Difficulty aside, it's just unnecessary.

H

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org


Mime
View raw message