I am liking the debugging console so far and I have some ideas on how to make it more useful. Maybe it already can do some of this, just point me in the right direction.
- Input properties used for a query.
In the Debug Console I can see a lot of data on the queries that were run. It would also be nice to know what the actual values were that were passed to the query. For instance in this query:
select max(RIGHT(invoice_id, 1)) as max_count from invoices where invoice_id like {{invoice_id_pre}} + '%'
What was invoice_id_pre actually? On a possibly related note, there is a place to see what the watchedParams are in the templateModel, but it is not populated.
- Table view of Query Dependencies
I can really see the potential in the Query Dependencies tab, but a big tree/map (what do you call that?) like that is of limited value as is. It would be nice to be able to drill down and say click on a query and see a list of its dependencies and dependents. Each of these would also be linked. And also maybe a filter on the tree/map so you only see the direct connects. Click one of those and only its direct contacts are displayed. Some system for navigating the ocean of data it can provide.