We have moved to GitHub Issues
Created by Mikael Syska 11 Jun 2013, 09:18:31 Updated by Sebastiaan Janssen 10 Jul 2013, 10:36:11
Two things ...
This is a little related to this issue: http://issues.umbraco.org/issue/U4-2353
Would it be possible to extend the mini profiler with additional information about what part of the code actually makes the SQL call? Like a callstack, method name, line number etc. to make future debugging of things easier?
The above is not really useful for knowing what is going on and what actually caused the call to the database. I can't tell, might be just me :-)
Would it be possible to include the Parameter the SQL was make with?
SELECT * FROM [cmsTemplate] INNER JOIN [umbracoNode] ON [cmsTemplate].[nodeId] = [umbracoNode].[id] WHERE ([umbracoNode].[nodeObjectType] = '6fbde604-4178-42ce-a10b-8a2600a2f07d') AND (umbracoNode.id = @0)
The above is almost perfect, but it would be nice to know what the "@0" parameter is in the SQL call, instead of using the MS SQL Profiler :-)
Yes, just set a SqlFormatter on Applicaton_Start:
StackExchange.Profiling.MiniProfiler.Settings.SqlFormatter = new SqlServerFormatter();
Thanks Meixger for pointing to the settings knowledgebase. I've increased the stacktrace to 5000 chars and added the SqlServerFormatter so that it shows the variable declarations above the query now.
Type: Feature (request)
Backwards Compatible: True
Due in version: 6.1.3