On 7 May 2011 14:51, Jeroen Vermeulen <j...@canonical.com> wrote: > On 2011-05-04 08:32, Gavin Panella wrote: > >> One approach to improving this situation could be to forbid (with >> code) the use of Reference properties that are not already cached (in >> the store cache; this is nothing to do with @cachedproperty). > > I'm a bit worried about the unusual cases: rarely-executed code paths, > unusual data, data that is usually cached but sometimes isn't, data that > falls out of the cache at an awkward moment.
Good point; this could be a problem with GenerationalCache. If many objects are loaded, and push things out of the cache such that they are garbage collected, code paths that might have been "fenced off" with this function in development might start failing in production. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
