Need to flush caches with modified object

Bug #593054 reported by Jamu Kakar on 2010-06-12
66
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

When I change the milestone on a bug, the milestone listing takes a
while to update and include the bug. It makes organizing bugs a bit
awkward, because I often jump around from bug to bug and then head
back to the milestone page and expect it to show me the results of
my work.

It does eventually update, but it takes a while.

Curtis Hovey (sinzui) on 2010-06-12
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
summary: - Milestone listing doesn't update (right away) when a bug is added to it
+ Need to flush caches with modified object
Revision history for this message
Curtis Hovey (sinzui) wrote :

There is not mechanism to say flush some caches of when an object is modified. The desired mechanism would permit the template to provide an additional key that a proc could call flush. In the case of milestones, I want a compose a key of project and milestone. When a bug or blueprint changes, my subscriber to the ObjectModifiedEvent could call flush_group(<launchpad-project-10.06>)

Curtis Hovey (sinzui) on 2010-06-13
affects: launchpad → launchpad-registry
Gary Poster (gary) on 2010-06-14
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Gary Poster (gary) wrote :

Speaking for Foundations, we want to update to provide automatic invalidation for our caches. We are currently experimenting with this in the webservice, and hope to bring that feature back to the browser-based interface after we've deployed and learned lessons on that side.

Revision history for this message
Martin Pool (mbp) wrote :
Revision history for this message
Curtis Hovey (sinzui) wrote :

The registry application is not going to use memcache in scenarios where the user can make changes and not see the updates.

Changed in launchpad-registry:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers