On Tue, Aug 10, 2010 at 8:59 PM, William Grant <[email protected]> wrote: > I think all POSTs redirect before displaying the subsequent page, so that > should be fine. However, I'm very suspicious of widely deploying > @cachedproperty... I'd be much happier if it was populated only by the > explicit prejoin, and operated uncached in the normal case.
We /need/ a strategy for doing non-collection derived data in the model, or we'll be playing 'omfg this is ugly shit', forever - and never getting things fast. Most of our pages only access 3 or 4 linked collections of objects, but they generally do well over a hundred queries: this is pathological! I think its better that we experiment and find the problems and fix them, than push back on actually getting what we need in place by making the problem bigger than it is: cachedproperty isn't ideal, but its a very small amount of work to use it. -Rob -- https://code.launchpad.net/~lifeless/launchpad/registry/+merge/32067 Your team Launchpad code reviewers is requested to review the proposed merge of lp:~lifeless/launchpad/registry into lp:launchpad/devel. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-reviewers Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-reviewers More help : https://help.launchpad.net/ListHelp
