-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01-Oct-2001 Tim Fox wrote: >> When the object is new or modified, call the db.load(). However, >> I guess my first question is why doesn't this load from the cache like a >> OQLQuery call would do? When the db.load() call is made, does the >> resulting object get cached? > I think you're right - you'll need to do an OQLQuery (as this bypasses the > cache) rather than a db.load (which looks in the cache first) Now I'm really confused. Originally, I had thought that both techniques (OQLQuery and db.load()) load from the cache. I think I asked about this specifically awhile ago. So, here's my question to 'those that know'... Do the objects that are returned from an OQLQuery get cached? Is it the case that only objects returned from db.load() are cached? Can someone verify that this is the case? Tim- If this is the case, then I still have a problem with app-layer distributed caching. My code needs a consistant way to retrieve objects. I can't use db.load() sometimes (when I want the cache) and OQLQuery other times (when I don't.) Especially if I want to notify different castor processes of changes to the cache. Basically, until the evict function is there, app-layer cache control is impossible. Virtually, Ned Wolpert <[EMAIL PROTECTED]> D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7uJrriysnOdCML0URAjZgAJ418Q+AeQZq7Ns5zFDvc9gHnvwB7wCfaf5G ngcIT+9pbJuE6oN+36nmcFs= =lnGB -----END PGP SIGNATURE----- ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
