Yes, go for C; use object composition, so that the contactinfo
instance is a property of the user instance.
On 1/4/06, Bobby Hartsfield <[EMAIL PROTECTED]> wrote:
> I'd agree with that. I'd personally lean more towards example C though.
> Since users can't exist without contact info, I don't see a
onent. There's definitely
nothing wrong with simplifying matters :-)
..:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.
Bobby Hartsfield
http://acoderslife.com
-Original Message-
From: Baz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 03, 2006 7:41 PM
To: CF-Talk
Subject: RE: Adding Multip
mplify matters...
Thoughts?
Baz
-Original Message-
From: Cornillon, Matthieu (Consultant)
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 03, 2006 3:56 PM
To: CF-Talk
Subject: RE: Adding Multiple Objects
Well, I would say that you can add contact info without adding a user
(multiple contacts,
That would probably depend on your database. How many tables do you have for
the users and contact info?
1 for contactinfo
1 for users
and a foreign key to relate the two... if so... the table with the
foreign key would be the LAST one to add since you'd need the id from the
other to complet
Well, I would say that you can add contact info without adding a user
(multiple contacts, right?) but you can't add a user without adding
contact info. So, it seems to me that you first instantiate the user
and then instantiate the contact info entry, not the other way around
(i.e., AddUser() firs
Not too sure what you're talking about here...
You should probably have a user object that has a contactinfo object inside
of it. These would be beans...
When you save the user bean to the database, you would run the validate
method on it first, which would validate all the fields inside user
6 matches
Mail list logo
