Hello,
Can some one please point me to any docs / info - on when is the cache loaded and used. Specifically I am referring to a quote from Bruce: "OQL goes straight to the database, whereas load() checks the cache first." I am looking for that type of details.
Any details on the following would help too!!!
1> In my app, I want to cache certain objects that are read only. But if I use OQL to query those objects, the cache will not be used- is that right? And I can use 'load' only using primary key so if I have to search objects based on non primary key � I need to use OQL � correct (or am I missing something very basic)?
2> There are some other objects that are read, edited and saved back - I don't plan to use a cache - as I do not see any value of doing that. Is this a correct assumption?
3>Even if do not use cache - 'dirty -checking' will still take place, right? In that case what I want to confirm is CASTOR will store the old value of the attribute I am modifying, for dirty checking.
For example lets say I have an Employee class with attribute deptId. When I queried the DB the value was '01'. Then I set it to '02'. When I commit CASTOR will verify that the deptId is still '01' and if it is, it will successfully update it to '02'. So some where CASTOR will store the old value '01' (at least logically, in reality it might verify dirty checking at each set method).
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
