I just got done figuring out how to --100%-- normalize a database to
make it very flexible. Methinks that Oracle has done this in some
fashion, as they claim to be able to make an intersection from any row
in any table to any other.
A note: Objects, Actors, and Attributes use the names of the tables
having 0:1 relationships to them as the value in their name .
Example:
Actors
ActorID=1,TypeID=1,Name=Company
ActorID=2,TypeID=1,Name=Company
ActorID=3,TypeID=2,Name=Member
Objects
ObjectID=1,TypeID=1,Name=Schedules
ObjectID=1,TypeID=2,Name=Bookings
ObjectID=1,TypeID=2,Name=Bookings
the database application code/constraints, or scripts accessing the
database have to enforce that no ObjectID,ActorID,AttributeID EVER gets
used twice and only appears in once of the tables in 0:1 relationship to
it.
I welcome any comments.
I've got the diagram in *.bmp (huge). I'll download a graphics program
and convert it to *.jpg. It'll be at:
http://64.177.230.204/public/VeryNormalised.jpg
http://64.177.230.204/public/VeryNormalised.png
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
