--//-
-Original Message-
From: Duncan [mailto:[EMAIL PROTECTED]
Sent: Monday, February 13, 2006 4:25 PM
To: CF-Talk
Subject: cfquery param vs cfif + N
What is the difference of doing this:
cfif getClient.saveAsUnicode eq 1N/cfif'#address#',
over this:
cfqueryparam value=#address
What is the difference of doing this:
cfif getClient.saveAsUnicode eq 1N/cfif'#address#',
over this:
cfqueryparam value=#address# cfsqltype=cf_sql_varchar
Is there a performance gain?
How does CF handle this differently?
Does cfqueryparam behave the same in 5,6 and 7?
Does SQL do anything
There is a theoretical performance gain, because the DB server can
cache they query plan, and just plug in differing values for different
queries. However, the more important benefit is SQL injection
protection.
To my knowledge the behaviour hasn't changed between 5 and 7, but I
could be wrong.
What is the difference of doing this:
cfif getClient.saveAsUnicode eq 1N/cfif'#address#',
over this:
cfqueryparam value=#address# cfsqltype=cf_sql_varchar
They're not comparable at all. The CFQUERYPARAM tag builds a prepared
statement and uses a bind parameter for your value.
Is there
Thanks for the info so far guys, useful links too.
I believe there is some sort of difference if you are using Unicode,
but I havent been able to put my finger on it - any info on that side
of things?
On 2/14/06, Dave Watts [EMAIL PROTECTED] wrote:
What is the difference of doing this:
Thanks for the info so far guys, useful links too.
I believe there is some sort of difference if you are using
Unicode, but I havent been able to put my finger on it - any
info on that side of things?
Specifying Unicode hints simply tells the database to treat a string as a
Unicode value.
6 matches
Mail list logo