The recordcount will persist if you have 'maintain connection' or pooled connections enabled for your datasource. Then it connects, and re-uses the existing connection over and over again. You can disable that and check how well it scales, it may add some overhead to your normal transactions. I have created a few DSNName_Nonpool connections to get around this issue, when I absolutely need to release a file at the end of a transaction, or am having configuration setting issues like this. Then switch any statement with a LIMIT over to the non-pooled, and you should be all set!
Chris Peterson Gainey IT Adobe Certified Advanced Coldfusion Developer -----Original Message----- From: James Wolfe Sent: Friday, July 13, 2007 12:53 PM To: CF-Talk Subject: Re: Query Result Problem >that seams to have worked for that query, but other queries still return a >limit of 50 records. So I have this question, that I could not answer myself >with a google search... Is possible that a SET ROWCOUNT x in one place would >affect every query from that server? Its possible that it would persist. I dont know if its a bug or if its by design. Either way, as Doug said, find the query that has SET ROWCOUNT 50 and make sure that at the end of that query, you SET ROWCOUNT 0 to reset the count to unlimited for all other queries. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 beta â Build next generation applications today. Free beta download on Labs http://www.adobe.com/cfusion/entitlement/index.cfm?e=labs_adobecf8_beta Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:283673 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
