Limitations of CFParam

[sillyworm]

I'm curious if someone can point me to any documentation regarding the limits
of the <cfparam> tag. More specifically, can it be used to set a default value
of a variable in the query scope? For example, could 'queryName.column1' be
given a value if the column is not actually defined in the query? From the
tests I've run, it seems like it cannot in fact write to vars in this scope,
but I want to make sure. The MM docs don't appear to touch this topic at all.
Thanks.

[gumshoe]

For example, could 'queryName.column1' be
given a value if the column is not actually defined in the query?

cfparam is not quite that smart. Actually, it has more to with the fact that
query objects cannot be written to in the way you are suggesting.

Your db should be able to help in this respect. You can either give a column
a default value when you create the table or, as in oracle, use the NVL()
function to give a column a default value should it be null in the returned
result set.

HTH



"sillyworm" <webforumsuser@macromedia.com> wrote in message
news:d08rrc$fce$1@forums.macromedia.com...

> I'm curious if someone can point me to any documentation regarding the
> limits
> of the <cfparam> tag. More specifically, can it be used to set a default
> value
> of a variable in the query scope? For example, could 'queryName.column1'
> be
> given a value if the column is not actually defined in the query? From the
> tests I've run, it seems like it cannot in fact write to vars in this
> scope,
> but I want to make sure. The MM docs don't appear to touch this topic at
> all.
> Thanks.
>