Comments on: Using cfqueryparam list attribute when using ‘IN’ operator http://www.pukkared.com/2011/01/using-cfqueryparam-list-attribute-when-using-in-operator/ Web Design & Development Wed, 10 Apr 2013 08:49:08 +0000 hourly 1 http://wordpress.org/?v=3.1.4 By: Acker Apple http://www.pukkared.com/2011/01/using-cfqueryparam-list-attribute-when-using-in-operator/comment-page-1/#comment-2436 Acker Apple Tue, 17 Jan 2012 21:14:40 +0000 http://www.pukkared.com/?p=1427#comment-2436 sorry guys, this post won't allow HTML code sorry guys, this post won’t allow HTML code

]]> By: Acker Apple http://www.pukkared.com/2011/01/using-cfqueryparam-list-attribute-when-using-in-operator/comment-page-1/#comment-2435 Acker Apple Tue, 17 Jan 2012 21:13:29 +0000 http://www.pukkared.com/?p=1427#comment-2435 I have found that I no longer like to use the list attribute for cfqueryparam as ColdFusion just creates a binded parameter per deliminated value. This causes a new execution plan to be created per number of listed items (one time a list has 6 attributes and another time only 2, this results in two execution plans in MS SQL). As of today, I send a list in as only one single cfqueryparam with list=”no” but I wrap the value sent in using a dbo.listToRows() function. Example: SELECT * FROM Table-Name WHERE column-name in (select * from dbo.rowsToList(,',')) --rowsToList is a SQL UDF that returns only one column of rows I have found that I no longer like to use the list attribute for cfqueryparam as ColdFusion just creates a binded parameter per deliminated value. This causes a new execution plan to be created per number of listed items (one time a list has 6 attributes and another time only 2, this results in two execution plans in MS SQL).

As of today, I send a list in as only one single cfqueryparam with list=”no” but I wrap the value sent in using a dbo.listToRows() function.

Example:
SELECT *
FROM Table-Name
WHERE column-name in (select * from dbo.rowsToList(,’,'))

–rowsToList is a SQL UDF that returns only one column of rows

]]> By: Acker Apple http://www.pukkared.com/2011/01/using-cfqueryparam-list-attribute-when-using-in-operator/comment-page-1/#comment-2434 Acker Apple Tue, 17 Jan 2012 21:12:13 +0000 http://www.pukkared.com/?p=1427#comment-2434 I have found that I no longer like to use the list attribute for cfqueryparam as ColdFusion just creates a binded parameter per deliminated value. This causes a new execution plan to be created per number of listed items (one time a list has 6 attributes and another time only 2, this results in two execution plans in MS SQL). As of today, I send a list in as only one single cfqueryparam with list="no" but I wrap the value sent in using a dbo.listToRows() function. Example: SELECT * FROM Table-Name WHERE I have found that I no longer like to use the list attribute for cfqueryparam as ColdFusion just creates a binded parameter per deliminated value. This causes a new execution plan to be created per number of listed items (one time a list has 6 attributes and another time only 2, this results in two execution plans in MS SQL).

As of today, I send a list in as only one single cfqueryparam with list=”no” but I wrap the value sent in using a dbo.listToRows() function.

Example:
SELECT *
FROM Table-Name
WHERE

]]> By: Jules Gravinese http://www.pukkared.com/2011/01/using-cfqueryparam-list-attribute-when-using-in-operator/comment-page-1/#comment-1694 Jules Gravinese Thu, 13 Jan 2011 15:49:13 +0000 http://www.pukkared.com/?p=1427#comment-1694 Very cool tidbit - thanks for sharing! Much better than using other functions to create the quoted value list first. Very cool tidbit – thanks for sharing! Much better than using other functions to create the quoted value list first.

]]>