Cfinvokeargument and trying to pass dates to a cfc/query

Question

Hi
I have a situation where passing a date along to a cfc method
(which runs a basic SQL select query) fails. if i hardcode the
datevalue into the cfc file or hardcode the select statement into
the page with the , it works. so something in the passing of the
argument is wrong but i cannot tell what. i have tried the
preservesinglequotes() function to no avail. Attached is a sample.
error: You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax
to use near '2008-02-29 21:23:17''
it seems as though if I set a variable (a whereclause)
variable with a date in it, the sql doesnt run right. I cannot say
"select * where #whereclause#" if the whereclause has a date
comparison value in it (where 'ending event date greater than now'
for example). what is the right way for me to pass this datetime
comparison command/argument in my cfm page to the cfc method? My
best guess not being a software engineer is that the MYSQL database
doesnt recognize the date ts{} if it's encapsulated in a larger
string variable. argh.
Thanks for the help smart people!
Brina

Answer 1

I tested it and it works fine. Though I noticed your query is
cached. Perhaps that is causing a problem. Try removing that
temporarily.
You can still construct the where clause dynamically with a
variable number of arguments. Just use WHERE 0 = 0 and append extra
conditions based on which arguments are defined.
SELECT Columns
FROM Table
WHERE 0 = 0
<cfif structKeyExists(arguments, "theDate")>
AND Eeventdate >= <cfqueryparam
value="#arguments.theDate#" cfsqltype="cf_sql_date">
</cfif>
<cfif structKeyExists(arguments, "id")>
AND ID = <cfqueryparam value="#arguments.id#"
cfsqltype="cf_sql_integer">
</cfif>
I would also suggest reading up on cfcomponent and
cffunction. It is important to scope function variables properly
using "var". This includes query names too. Proper scoping prevents
threading problems for cfc's that are stored in a shared scope.
Also, it is good to get into the habit of including function return
types, argument types, etcetera. It improves readability and also
provides type checking.