Hello folks: Thanks to all who replied--I really appreciate your thoughts and insights on the issue.
Here is the latest development on my fascinating CFQueryparam issue: 1. I have gone through the error messages on this issue, and none of them has bad data coming in. Which is to say, all the incoming data for cookie.theID conforms to somehting like "123456", 6-digit integers. So, in all instances, something happened with the cfqueryparam tag, where incoming values all got somehow translated into "521636a". 2. The incoming data is supposed to be for an ID column, which is of VARCHAR data type in the database, and it auto increments. It is not designed to be hexadecimal, so I can't imagine the translated value standing for any hexadecimal either--well, at least there is no instruction on either the CF or MSSQL side which tells it to convert into hexadecimal. Adding to the confusion of course, is that this ID column is sometimes VARCHAR and sometimes INT in different tables--probably not the best practice. We have an archaic system (iMIS) and it has this ID as VARCHAR, but elsewhere, in built-in-house systems sometimes it is INT. Regarding Brad's comment: I am intrigued by the theory of corrupted cached SQL statement... What exactly does that mean? How does corrupted statements get cached? And if it was corrupted, how/why did it run before with no issues? Did something happen that made the corrupted cache stop working? Thanks guys for your thoughts! On Tue, May 12, 2009 at 5:23 PM, Jason Fisher <[email protected]> wrote: > > Ummm, not sure why your cookie.theID would shift, but I would say > absolutely that the CF_SQL_TYPE is designed to match the database column > data type, not the incoming variable parameter. The entire point of the > CF_SQL_TYPE is to let the JDBC driver handle the data pass-through for you > in a way that is safe and that the database server understands, regardless > of what RDBMS you are using. > > So, I would agree that there are 2 separate issues: what's gone on with > your data, independent of the CFQUERY and then ensuring that all > CFQUERYPARAMs are designed to match your database rather than your > application data, which in this case just happens to be integer. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:322513 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
