web2py trunk has db._timings which contains a log of all SQL queries.
This means if you add to a page
{{=BEAUTIFY(request)}}
{{=BEAUTIFY(response)}}
{{=BEAUTIFY(session)}}
{{=BEAUTIFY(db._timing)}}
You get almost all info as a django toolbar. If you run with --
profiler profiler.log you get profiler info into profiler.log. That is
a lot of info. we need to decide how to display it.
For example. If the page returns an error (a ticket) do we want to
collect all the info so that it can be retrieved from the toolbar?
Where should it be logged? In a hidden db table? How can we retrieve
it? Should we tag every http request with a uuid?
I could also use some help in the JS/CSS to display the toolbar. How
should it look like? Should the toolbar be loaded via ajax or should
the associated page be loaded into an iframe?
Ideas would be appreciated.
Massimo
