Differences

This shows you the differences between two versions of the page.

--- mantisbt:performance_counters_requirements [2006/12/23 02:10] – More ideas and some schema changes vboctor
+++ mantisbt:performance_counters_requirements [2011/11/16 07:38] (current) – The page rendering was broken (maybe since new PHP version on mantisbt.org). Added new line to fix it at end of file. atrol
@@ Line 88: / Line 88: @@
      * Ability to use saved filters to calculate values for counters.  For example, number of issues matching a filter would be the value of the counter.
      * Template Counters - it would be very useful to have a counter that counts the number of open issues for a developer or a category, then be able to run this counter for every developer or every category, rather than having to define a counter record per developer or per category.
 ===== Feedback =====
-Put your feedback in this section.
+I don't understand the original premise, that Mantis only has a snapshot of information as at the current time. It already contain hsitorical data with fields storing when a task was submitted, etc. So the example above "number of issues that has priority 1 and have been open for more than 3 days" is already trivial. ''SELECT * from  bug WHERE date_submitted > now() - 3 AND priority = 1''
+In projects I've worked on, de-normalising the database in this way has often created a lot more work in the long term than just building more advanced queries. If there is historical information which is lost over time, then perhaps an extra table to keep that information in a revisioned format would be a better option. But from what I've seen so far of Mantis, this appears to not be a problem. --- //aristedes 2007/04/14 04:04//