I think you are on the right track but missed the business rules end of OO.
I would do the same as you - create objects for dealing with my underlying
tables. I call these objects data access components, and normally store
them in a different folder called data. Now, you have the concept that
myself? ;^)
Jim Davis
-Original Message-
From: Shawn Grover [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 3:56 PM
To: CF-Talk
Subject: RE: OO modeling Hell
I think you are on the right track but missed the business rules end
of
OO.
I would do the same as you
, so my examples might be completely off...
HTH.
Shawn
-Original Message-
From: Jim Davis [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 2:36 PM
To: CF-Talk
Subject: RE: OO modeling Hell
I think I misrepresented my problem.
The objects are virtual - they have no database
In this case then...
A specific event object would have a property for venue, and another
for
time slot. These properties would be of type Venue and type Timeslot
respectively (that is, Event.Time would be a timeslot object based on
the
timeslot class, and Event.Venue would be a venue
Message -
From: Jim Davis [EMAIL PROTECTED]
Date: Thursday, September 18, 2003 2:35 pm
Subject: RE: OO modeling Hell
I think I misrepresented my problem.
The objects are virtual - they have no database access themselves
(this is handled, as you suggest, by separate implementation classes
My initial idea was to have a Performances (or perhaps Showings)
property in Event that was a two dimensional array of TimeSlot/Venue
references.
Sound good?
I think an EventCollection object would work better in this case.
this, but hopefully I've helped you understand things enough to be able to
make the choice.
HTH.
Shawn
-Original Message-
From: Jim Davis [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 3:34 PM
To: CF-Talk
Subject: RE: OO modeling Hell
I'm getting it I think... one point
Sounds like you're on the right track.
Regarding your sample approach below, I'd have to say that this
depends on
how you want to code it, and what the requirements of your application
are.
You could have one event object that contains an array/collection of
time
slots and venues, or you
8 matches
Mail list logo
