18:56 < BjornT> salgado: i don't think Bug.bugtasks should be made into a cachedproperty, but i think you're on the right track. it might make sense to create a new method, that builds a list of all
the conjoined bugtasks (or non-conjoined ones)
18:57 < salgado> BjornT, why you don't think it should be made into a cachedproperty?
18:57 < BjornT> salgado: because you have to ensure that the cache is invalidated when it should be; and that's not so trivial.
18:58 < BjornT> salgado: and, you want to avoid one query per bug
18:59 < BjornT> salgado: using a cachedproperty will still issue one query, so things won't improve that much.
18:59 < salgado> BjornT, can you comment on the bug so that we have this discussion stored there?
18:59 < salgado> BjornT, that by itself, yes. but my plan is to roll my own search function which would pre-fill the cache
19:02 < BjornT> salgado: that sounds a bit complicated. given the issue with invalidating the cache, i'd say a separate method is more doable.
18:56 < BjornT> salgado: i don't think Bug.bugtasks should be made into a
cachedpropert y, but i think you're on the right track. it might
make sense to create a new method, that builds a list of all
cachedproper ty?
invalidated when it should be; and that's not so trivial.
things won't improve that much.
discussion stored there?
search function which would pre-fill the cache
invalidating the cache, i'd say a separate method is more
doable.
the conjoined bugtasks (or non-conjoined ones)
18:57 < salgado> BjornT, why you don't think it should be made into a
18:57 < BjornT> salgado: because you have to ensure that the cache is
18:58 < BjornT> salgado: and, you want to avoid one query per bug
18:59 < BjornT> salgado: using a cachedproperty will still issue one query, so
18:59 < salgado> BjornT, can you comment on the bug so that we have this
18:59 < salgado> BjornT, that by itself, yes. but my plan is to roll my own
19:02 < BjornT> salgado: that sounds a bit complicated. given the issue with