It's worth mentioning that many languages that promote the "collection of objects" approach over the "record set or query" approach do so at least in part because the concept of a record set is not built in to the language - for example, if you wanted to pass a record set to the view layer of your java app, your view layer components would have to import java.sql.RecordSet, which would be messy (tier leakage - why should a view tier component know about a data-tier related concept?)
Meanwhile, in cf, a query is a central concept of the language - you don't have to import anything and many tags like cfoutput and cfloop are tightly integrated with queries. Not only that, but lots of other tags and functionalities that have nothing to do with databases also produce queries - like cfdirectory, cfsearch - heck, even cfhttp. /t >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Brian Kotek >Sent: Tuesday, September 13, 2005 3:53 PM >To: [email protected] >Subject: Re: [CFCDev] Multiple results from a query passing into a bean > >Beans are generally meant to wrap up data for a single entity. IE a >single product for a product details page. If you are displaying a >list of 10 product names and prices it is overkill >to create 10 Product objects. In most cases you can just use a query >result set when working with sets like that. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
