Title:
Bug 73804:(Watson Migration Closure)It would be really helpful if the debugging output would provide a couple of simple enhancements for the current option to track query times
| View in TrackerStatus/Resolution/Reason: Closed/Deferred/NotEnoughTime
Reporter/Name(from Bugbase): Charlie Arehart / charlie arehart (Charlie Arehart)
Created: 11/26/2008
Components: Debugging, General
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 0
Problem:
It would be really helpful if the debugging output would provide a couple of simple enhancements for the current option to track query times.
1) It would be helpful if we were shown a total of the time spent in queries. Right now, we have to manually add up each query's reported time. Sure, the ColdFire add-in (for Firebug on Firefox) does this, for those using that, but it really ought to be in the core product.
2) While we're at it, it would be nice also for the times shown (in the TIME=) display for each query to have commas for thousands. It's easy to misread 125ms as 12 seconds, given the small italicized type, as one is eyeballing times reading down the page.
3) Similarly, it would be nice to highlight those queries that take more than a given amount of time. This is already in place for pages, where the CF Admin page for debugging settings has an option to highight in red those include files or CFC method calls that exceed a specified time (defaults 250ms). You could either use that time, or add a separate time value if people wanted to highlight long-running queries separately.
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3036837
External Customer Info:
External Company:
External Customer Name: charlie arehart
External Customer Email: 03D0090C44723473992015D5
External Test Config: 11/26/2008
Attachments:
Comments: