Added sterner warning about debugging old CBORM versions

michaelborn · web-flow · commit 9438909ec022 · 2021-04-13T09:04:06.000-04:00
diff --git a/readme.md b/readme.md
@@ -377,7 +377,9 @@ cborm : {
 }
 ```
 
-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.
+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.
+
+> **Note**: CBDebugger's `cborm.logParams` setting requires CBORM 3.2.0 or higher.
 
 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.
 

Original file line number	Diff line number	Diff line change
`@@ -377,7 +377,9 @@ cborm : {`
`377`	`377`	`}`
`378`	`378`	```
`379`	`379`
`380`		-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.
	`380`	+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.
	`381`	`+`
	`382`	+> Note: CBDebugger's `cborm.logParams` setting requires CBORM 3.2.0 or higher.
`381`	`383`
`382`	`384`	`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.`
`383`	`385`