I think Patrick got the jist of it. If you have a form that allows creating a user, a contact, and an employee, then it sounds like you've got three entities (a user, a contact, an employee), and you just happen to be using the same information for each one. So I'd expect the app to create a user object, persist it with a user DAO, then create a contact, persist it, and finally create an employee and persist it.
Now, if you have entities that extend one another (for example GenericFile and FlashFile in a CMS), then it's very likely that your FlashFile DAO will deal with both the generic_file and the flash_file tables in your database, if you've set up your DB to have table-level "inheritance." cheers, barneyb On 9/15/05, Nick Han <[EMAIL PROTECTED]> wrote: > Barney, can you reduce the language down like a fraction so I can > understand better on what you just said? Ok, for a DAO example, I have > a form that will insert information about the user into users table, > contacts table, and employment table? Will I have one DAO to do all > this or 3 separate DAOs, one for each table? It sounds like what you > said is that there should only be one DAO? Thanks in advance. > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ---------------------------------------------------------- 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]
