Re: Caching by pre-loading

*From:* James Johnson [mailto:[EMAIL PROTECTED] *Sent:* Thursday, 04 January 2007 19:32 *To:* user-java@ibatis.apache.org *Subject:* Re: Caching by pre-loading Thanks for the quick response. "iBATIS caches by SQL statement". I thought that was the case. Thanks for confirming. I'

RE: Caching by pre-loading

give you better results. Christian From: James Johnson [mailto:[EMAIL PROTECTED] Sent: Thursday, 04 January 2007 19:32 To: user-java@ibatis.apache.org Subject: Re: Caching by pre-loading Thanks for the quick response. "iBATIS caches by SQL statement"

Re: Caching by pre-loading

Thanks for the quick response. "iBATIS caches by SQL statement". I thought that was the case. Thanks for confirming. I'm trying to just use iBatis caching. One way that I saw of accomplishing pre-loading was to issue the "select * from employee" at web application startup. Then, on each user req

Re: Caching by pre-loading

iBATIS caches by SQL statement - your two statements are different, so there is a cache miss. This also demonstrates a fundamental truth about iBATIS - iBATIS doesn't know about object identity. So iBATIS would have no way of looking through the first set of cached results to see if an object fr

Caching by pre-loading

How does iBatis determine whether results are to be pulled from the cache or to be queried from the database? For instance, if I have a query like such: "select * from employee" and then follow-up with a second query of "select * from employee where id=1", the second query appears to hit the datab