I'm somewhat surprised to hear you say that Patrick. What if there are 500 different membership types? 500 subclasses of member? Yikes. Hello class explosion.
On 8/20/07, Patrick McElhaney <[EMAIL PROTECTED]> wrote: > > On 8/20/07, Justin Treher <[EMAIL PROTECTED]> wrote: > > > My object is composed of another subject (member class has a > > membershipType class). > > That doesn't sound very object-oriented to me. Would it make sense to > have an abstract class, member, and have each membership type be a > subclass of member? > > (See Joe Rinehart's excellent article on not letting the relational > model drive the domain model: http://tinyurl.com/2kqg4z) > > > -- > Patrick McElhaney > 704.560.9117 > > > You are subscribed to cfcdev. To unsubscribe, please follow the > instructions at http://www.cfczone.org/listserv.cfm > > CFCDev is supported by: > Katapult Media, Inc. > We are cool code geeks looking for fun projects to rock! > www.katapultmedia.com > > An archive of the CFCDev list is available at > www.mail-archive.com/cfcdev@cfczone.org > > You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
