On 10/27/05, Cliff Meyers <[EMAIL PROTECTED]> wrote: > I don't know about that. If I already have a User object to model a > single user why should the representation of a large number of users > be anything but a collection of User objects? I'd much rather have a > consistent "interface" to a user's data than having one approach for > single entities (getter methods) and another for batch data (direct > access of database column names).
It's not necessarily bad thing, it's just a lot of overhead that may or may not be beneficial given the particular situation in which you find yourself. I'm with Dave--the query object is darn handy and I personally don't avoid it just to try and be more "OO." Everything has its place. -- Matt Woodward [EMAIL PROTECTED] http://www.mattwoodward.com ---------------------------------------------------------- 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]
