It's worth mentioning (again) that many languages that promote the collection of objects approach over using recordsets do so at least in part because the language has no default built-in recordset datatype - which is not the case with cf.
>-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of David Ross >Sent: Thursday, October 27, 2005 5:53 PM >To: [email protected] >Subject: Re: [CFCDev] Race Conditions when scoped in >theApplicationvariable > >Well, I think CF's query is a great abstraction and should be used when >appropriate. When you have a "listing" page, it's going to be easier to >work with a query than a list of objects. While languages that >have more >OO features tend to lean towards lists of objects, I don't think using >queries makes your model not OO... think of a query of users as a >"UserListing" object. It contains aggregate data about a set >of objects, >and it has many features that would difficult to implement if you used >something else (think QofQ). Again, it's an "abstraction" of a bunch of >objects, and I don't think that makes your model any less OO. > >-Dave ---------------------------------------------------------- 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]
