> Ok, removing the trigger makes it easier to keep things sane. How do you
> intend to keep the other values up-to-date?
The other values will be kept up-to-date with a cronjob.
> Maybe it makes sense to rename
> them, so that it's clear that they are caches only, and might not be correct?
> Unless you find a way of making sure they are up to date, of course.
Although I was originally thinking of updating the values with a cronjob, the max_bug_heat is currently updated with a hook in addTask(), so it would be easy to add that. I assume that I could do something similar for po_message_count.
> Also, for
> the bug values, will it include private bugs as well?
> Ok, removing the trigger makes it easier to keep things sane. How do you
> intend to keep the other values up-to-date?
The other values will be kept up-to-date with a cronjob.
> Maybe it makes sense to rename
> them, so that it's clear that they are caches only, and might not be correct?
> Unless you find a way of making sure they are up to date, of course.
Although I was originally thinking of updating the values with a cronjob, the max_bug_heat is currently updated with a hook in addTask(), so it would be easy to add that. I assume that I could do something similar for po_message_count.
> Also, for
> the bug values, will it include private bugs as well?
Yes.
> The comments should be added to comments.sql.
The comments have been moved.