Oracle uses cfqueryparam to bind vars
If you don't, the DB Query Engine (or summat) will treat them as dynamic
bind variables and although it probably doesn't harm that much to have
them in cfqueryparam, they aren't bind vars... they are constants thus
don't need it
... trying to find the link to it in the archives at the moment to the
discussion
--
dc
-----Original Message-----
From: Ian Skinner [mailto:[EMAIL PROTECTED]
Sent: 08 December 2003 18:36
To: CF-Talk
Subject: The Value of CFQUERYPARAM
When writing a select statement, if I have a part of a WHERE clause that
will be static, always the same value, and this value is not passed in
with a variable or constant, is there any inherent value in
<cfqueryParam ...> tags?
An Example:
WHERE STATUS = <cfqueryParam value="M" ...>
or
WHERE STATUS = 'M'
Is there any real advantage of one of these forms over the other?
Just to repeat, these are hard coded, unchanging values NOT passed in
with variables or constants. I understand the value of the
<cfqueryParam> tags in conjunction with passing in data with variables,
especially data from user forms.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
