On Wed, Aug 18, 2010 at 2:18 AM, Curtis Hovey
<email address hidden> wrote:
> Review: Needs Information
> MilestoneView._bugtasks uses precache_permission_for_objects() on the bugtasks and the conjoined bugtasks. Does this change allow us to remove precache_permission_for_objects()? Will your test fail if I remove precache_permission_for_objects() from the view?
For objects queries via that search path, the precaching be removed. I
do not know if getConjoinedMaster accesses the related objects via
that code path - and I suspect in fact that it does not.
> MilestoneView._bugtasks calls getConjoinedMaster() with a prepared list (1 query) of expected ids. I think we need to keep behaviour; this branch just lowers the access cost of getConjoinedMaster()
We can refactor the conjoined master stuff too, but its a separate issue IMO.
On Wed, Aug 18, 2010 at 2:18 AM, Curtis Hovey _bugtasks uses precache_ permission_ for_objects( ) on the bugtasks and the conjoined bugtasks. Does this change allow us to remove precache_ permission_ for_objects( )? Will your test fail if I remove precache_ permission_ for_objects( ) from the view?
<email address hidden> wrote:
> Review: Needs Information
> MilestoneView.
For objects queries via that search path, the precaching be removed. I
do not know if getConjoinedMaster accesses the related objects via
that code path - and I suspect in fact that it does not.
> MilestoneView. _bugtasks calls getConjoinedMas ter() with a prepared list (1 query) of expected ids. I think we need to keep behaviour; this branch just lowers the access cost of getConjoinedMas ter()
We can refactor the conjoined master stuff too, but its a separate issue IMO.
-Rob