On Thu, Mar 31, 2011 at 6:56 PM, Martin Pool <[email protected]> wrote:
> I can see how lbyl access checks for every bug in a table could get
> expensive.  If this is rolled out more widely, possibly we should not
> lbyl but rather just give an error if the user tries to change
> something they're not allowed to change.

Right - we have a /long/ way to go to make bug performance acceptable,
or even great; In the context of this thread - quick n dirty - I
wanted to suggest that taking on the bigger issues is not quick - and
that a performance regression is too dirty.

-Rob

_______________________________________________
Mailing list: https://launchpad.net/~launchpad-dev
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~launchpad-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to