>two quick questions: >1) Do you think of that form as the "user edit form"? Or do you think of it >as the "user, contact, and employment edit form"? >2) Are there other things in your app that *also* have contact info and/or >employment info, but are not users?
Tanguy, Having read other people's emails this morning about this topic, I think I know where you are heading with these questions. But I am interested to hearing your take. Ok, For question #1, let's say I think of the form as "user edit form". This edit form has user's login info (like username and password in the users table), has user's contact info (like work address, home address, emergency address in the contact table), and has employment info. So upon this edit action, the update will hit all three tables. Given this scenario, how would I set up my DAO(s)? One DAO that does all this? Give me some pseudo code to look at. For question #2, let's say the users table is the parent table, and no contract info or employment info will exist without having a relational id to the users table. (1 users record to one or many contacts or employment info). Thanks in advance for your input. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RADEMAKERS Tanguy Sent: Thursday, September 15, 2005 12:19 PM To: [email protected] Subject: RE: [CFCDev] Table joins DAOs >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. two quick questions: 1) Do you think of that form as the "user edit form"? Or do you think of it as the "user, contact, and employment edit form"? 2) Are there other things in your app that *also* have contact info and/or employment info, but are not users? /t ---------------------------------------------------------- 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] ---------------------------------------------------------- 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]
