-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30.04.2014 02:58, Christopher Nelson wrote: > I'm not sure what you mean by "side effects on changes resources."
I meant effects on just changed resources, what could even lead to infinite recursion in worst case. > My change listener only writes to its own private tables but it > reacts to changes in data managed by MasterTickets. There are > reasons that it is more efficient to read the mastertickets relation > than rely on the custom blockedby and blocking fields but I can't > always know if mastertickets is up to date. Ticket custom field storage is not the most efficient one, if you need to get out a lot of information quickly, not to speak of indexing or the like. I can imagine that one uses own, private storage for efficiency, sure. OTOH I hope we could do better in core. A flexible db table view comes to my mind, that could refit automagically depending on custom fields configuration. But I'm not so much an db expert to decide, if that would really matter for performance. Steffen Hoffmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNgwhMACgkQ31DJeiZFuHcf4QCgg7S1V90/GoZHX0aomjGqkwOl OtIAoN5h1735w+cMCd55kBA2IqCCVhLx =7OWu -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
