Part of good db design is to plan way into the future. Your customers
may only have one account now, but is it possible in the future they could
have 2? These are HUGE decisions that can come back with really big teeth.
Well, this is all in an example. Even if a customer could have more than
one accounts, allowing for a many:many, I'd still have the same issue
figuring out naming schemes.
What is a service?
"Email Hosting", "Web Hosting", etc. But I'm not designing a billing
system. This is just an example. But I'd have these same questions if I
was listing something else, like a forum, etc.
_______________________________________________
New York PHP User Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/show_participation.php
