Is there a way to avoid the error and avoiding the need to write seperate queries

quote:

---

Originally posted by: nikos101
I just changed they type in CF to string and it wasn't fussy anymore

---

If the db field is integer, send your function a non-numeric string and see how fussy your db gets.

> Do some if/else logic to create a variable that will be either true or false, depending on whether
> or not arguments.forwardvalue is an integer. Then use that variable in the null attribute of cfqueryparam.

I think CF always validates the value, even when you are using the null attribute. So you may have to resort to using val(arguments.forwardValue) in combination with the if/else logic for the null attribute

<cfqueryparam value="#val(arguments.forwardValue)#"
cfsqltype="cf_sql_integer"
null="#not IsNumeric(arguments.forwardValue)#">