I imagine that you get some overhead if you call up some large datasets, but that's why I can call a limited size collection from the DB - it's rarew to need the entire recordset of data.
It's quite the opposite approach to really optimizing your queries for lighting-quick response times from the db, but the advantage is OOP and maintenance. Even so, I think it could be optimized to be quite fast by using SPs (which I do). You can also extend this with your own methods of grabbing data from the database that would be much faster (such as passing in a list of ids to grab, or indicating that you'd like only a list of ids from the db) that would keep your performance at the levels you'd like to maintain. But I agree with you, this is probably not the thing to use if speed is all that matters to you. - Matt Small -----Original Message----- From: Kevin Graeme [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 18, 2005 2:02 PM To: CF-Community Subject: Re: ASP.net 2.0 Thanks for the writeup. That's close to what my understanding of it was. We heavily leverage SQL with complex queries to get Oracle to do the heavy massaging of the specific data requests. That appears to be the opposite approach to using a DAO. Doesn't it get pretty memory heavy and slow to process large recordsets? I know that we (Deanna) has spent a lot of time optimizing queries to get processing times down. And we've got hundreds of subsites all running on the one server. -Kevin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:5:158092 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
