From: Matthew B. <mat...@ou...> - 2007-03-05 10:53:52
|
At the moment softcache will cache and then serve up anything that it has. This could case problems if someone pulls some data out of softcache, modifies it but doesn't save it back to to db (because of transient problem or because of programmer error). But softcache will still return it but the changes won't be in the database. Should we only cache stuff that has been successfully saved? I think we can just check isUnsaved() on all object going in and out of softcache which should catch any of these problems and the overhead on doing this is pretty low. -- Matthew Buckett |