#613: Add / remove milestone breaks a whole product
---------------------------+-----------------------------------------------
Reporter: olemis | Owner: gjm
Type: defect | Status: accepted
Priority: blocker | Milestone: next 0.x
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords: milestone, postgresql, db, sqlite
---------------------------+-----------------------------------------------
Comment (by gjm):
Replying to [comment:21 wimh]:
> Replying to [comment:20 gjm]:
> > With luck the commit is a good enough solution for now.
>
> It fixes the problems for me, but do I understand it correctly it
flushes all caches each time for each request? At least in the
{{{MilestoneCache}}} it looks like a new SQL query is done each time I
refresh the milestones admin page.
It is only intended to flush a specific cache but there may be
consequences for other caching. I haven't gone through all the
implications which is part of the reason that I haven't closed this ticket
yet.
Effectively the solution should be safe enough though there is likely to
be some degradation in performance. Given that changes in milestone are
relatively rare this could look like an overreaction.
If this requires further discussion, it might be better to discuss it on
the dev mailing list as it should get a wider audience.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/613#comment:22>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
