You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Track all cbdebugger events, by default this is off, turn on, when actually profiling yourself :) How Meta!
91
+
trackDebuggerEvents :false,
89
92
// Store the request profilers in heap memory or in cachebox, default is cachebox
90
93
storage :"cachebox",
91
94
// Which cache region to store the profilers in
@@ -149,7 +152,7 @@ moduleSettings = {
149
152
cborm : {
150
153
enabled :true,
151
154
expanded :false,
152
-
// Log the binding parameters
155
+
// Log the binding parameters (requires CBORM 3.2.0+)
153
156
logParams :true
154
157
},
155
158
// Async Manager Reporting
@@ -177,12 +180,12 @@ This module will also register a few methods in all your handlers/interceptors/l
177
180
178
181
```js
179
182
/**
180
-
* Method to turn on the rendering of the debug panel on a reqquest
183
+
* Method to turn on the rendering of the debug panel on a request
181
184
*/
182
185
any functionshowDebugger()
183
186
184
187
/**
185
-
* Method to turn off the rendering of the debug panel on a reqquest
188
+
* Method to turn off the rendering of the debug panel on a request
186
189
*/
187
190
any function hideDebugger()
188
191
@@ -371,12 +374,14 @@ We have a dedicated panel in the debugger that will track all criteria queries a
371
374
cborm : {
372
375
enabled :true,
373
376
expanded :false,
374
-
// Log the binding parameters
377
+
// Log the binding parameters (requires CBORM 3.2.0+)
375
378
logParams :true
376
379
}
377
380
```
378
381
379
-
You can also select to `logParams` and we will track the original executable parameters of the query so you can debug the actual values of these executions. We will also track from WHERE in the application the sql execution came from and you can even open the file to that specific line number using our code editor integrations by clicking our **open in editor** buttons.
382
+
You can also enable `logParams` and we will track the original executable parameters of the query so you can debug the actual values of these executions. We will also track from WHERE in the application the sql execution came from and you can even open the file to that specific line number using our code editor integrations by clicking our **open in editor** buttons.
383
+
384
+
> **Note**: CBDebugger's `cborm.logParams` setting requires CBORM 3.2.0 or higher.
380
385
381
386
The grouped view you see above will give you an aggregate look of all the sql calls made during the request and their frequency of execution. It will also give you a mini report of those specific sql groups with data about where the query originated from in your source code and the binding parameters, if activated.
0 commit comments