I don't know Oracle, but in SQL Server global temp tables are by design available to all connections. (##table_name) If you were using them, wouldn't you expect them to be shared?
On the other hand, regular temp tables (#table_name) are per connection, but isn't it proper to drop them after usage if for no other reason than to not have them laying around later if a connection is reused? ~Brad ----- Original Message ----- From: "Craigsell" <[email protected]> To: "cf-talk" <[email protected]> Sent: Friday, January 30, 2009 10:16 PM Subject: Re: Connection pooling - why bother? > > There is one other thing to consider in using connection pooling. I admit > it is a bit off the beaten path but it bit me pretty good. I use Oracle > stored procedures as much as I can. You cannot use connection pooling if > your stored proc uses Global Temporary Tables. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:318701 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
