It might have been a problem on the SQL server side if a corrupted prepared statement got cached. Changing the cfsqltype effectively cleared the old statement since a new one needed to be recompiled. Can't say I've ever seen what you described but I have seen structure changes a database break cached prepared statements before.
~Brad -------- Original Message -------- Subject: my cfqueryparam grievance From: Qing Xia <txiasum...@gmail.com> Date: Tue, May 12, 2009 2:16 pm To: cf-talk <cf-talk@houseoffusion.com> Hello folks, I had a pretty strange experience with CFQueryParam today. Basically, I have an innocent-looking query: <cfquery datasource="#application.myDB#" name="qGetUser"> *SELECT* username, password *FROM* someTable *WHERE* someID = <cfqueryparam cfsqltype="CF_SQL_INTEGER" value= "#cookie.theID#" maxlength="6"> </cfquery> This query had worked just fine for nearly a year (since I cfqueryparamed it last summer) until this morning, when it broke. The error messages read: *Message:* Error Executing Database Query. 12 May 2009 01:49:21 PM EDT Diagnostics: Error Executing Database Query. [Macromedia][SQLServer JDBC Driver][SQLServer]Syntax error converting the varchar value '521636a' to a column of data type int. The error occurred on line 35. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:322441 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
