> Option 1 means that you must write and maintain all > insert/select/update/delete SQL for your app? > Is that correct?
Yes. Into every life a little SQL must fall. I think you'd find, however, that writing SQL for individual types to be persisted is less work than cooking a metadata scheme that allowed generic DAOs to create effective SQL on the fly. If nothing else, I wouldn't want the performance overhead of doing that for every read/write. > OK, its been a while since I went to school, and im fully prepared to be > wrong, but option 2 uses Polymorphism, option 1 doesnt? Kind of backwards - without type, polymorphism can't take place. Option 2 gives no repect to type in that it accepts anything, never checking to make sure that what it's passed is of the form (as in polymorphism = "many forms") that's required. Option 1 regards type - it'd accept a given type or any subclasses of that type. -joe -- For Tabs, Trees, and more, use the jComponents: http://clearsoftware.net/client/jComponents.cfm ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
