It doesn't cache the query. Your database will know how to process the query faster because the parameters will be typed (instead of receiving a long string of text to execute, it receieves the query like a stored procedure, and passes it variables).
very strange. the query wasn't in an application.queryname (or session etc) scope by any chance? >>> [EMAIL PROTECTED] 06/01/05 10:55 am >>> Can someone tell me how CFQUERYPARAM actually works? I understand it caches the query, but where? in the CF server or the database server? I just had an issue where I changed a query due to a column being added into a table, and the query used the CFQUERYPARAM tag. For some reason, the columns being returned by the query did not change. I changed the name of the query and it still didnt work. This is what i had /////////////////////////////////// SELECT col1, col2, col3 FROM Table WHERE ID = <cfqueryparam value="#Arguments.ID#" cfsqltype="CF_SQL_INTEGER"> /////////////////////////////////// I then added an extra column to the table I then changed the query to /////////////////////////////////// SELECT * FROM Table WHERE ID = <cfqueryparam value="#Arguments.ID#" cfsqltype="CF_SQL_INTEGER"> /////////////////////////////////// and it still only returned the 3 columns in the first example. the only way i could get it to pick up the additional column was to remove the cfqueryparam tag Can anyone shead some light on this? Regards Steve Onnis --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
