Null attribute in cfprocparam - is this a bug

[jimmyshoes]

I'm using cf8

<cfprocparam type="in" null="true" value="#Trim(arguments.attributes.strCircuit)#" cfsqltype="cf_sql_varchar">

If null is true I thought that the value attribute would be ignored
Yet the following code generates this error
Element ATTRIBUTES.STRCIRCUIT is undefined in ARGUMENTS.

Is this a bug?

 

[jimmyshoes]

To clarify the above
Shouldn't the code below work, instead it says that varNotDefined is undefined

<cfprocparam type="in" null="true" value="#varNotDefined#" cfsqltype="cf_sql_varchar">

 

[FALCONSEYE]

<cfprocparam type="in" null="true" value="#varNotDefined#" cfsqltype="cf_sql_varchar">

varNotDefined is not defined. why don't you do something like this before the cfproc?

<cfif Not IsDefined('varNotDefined')>
<cfset varNotDefined = ''>
</cfif>

http://www.fuzzysiberians.com

 

[cfSearching]

If null is true I thought that the value attribute would be ignored
Yet the following code generates this error
Element ATTRIBUTES.STRCIRCUIT is undefined in ARGUMENTS.

Yes, the description could be improved. Strictly speaking it means CF will send a NULL to the database instead of whatever you have for the "value". So CF always evaluates your variable, whether it is used or not.

----------------------------------

http://cfsearching.blogspot.com/

 

[DigitalRedneck]

or you could do this:

<cfprocparam type="in" <cfif IsDefined('varNotDefined')>
value="#varNotDefined#" <cfelse>null="true"</cfif>cfsqltype="cf_sql_varchar">

 

[cfSearching]

I think FALCONSEYE's approach has better readability.

Another possibility might be to just set the default within the cfargument tag.


----------------------------------

http://cfsearching.blogspot.com/