Your link approach is fine (and I consider it preferable).
Assume you suddenly start selling ties. With the Link_type approach, you simply need
to create a new link type and you're ready to roll. Much simpler than needing to
create a new table/relationship.
Also, suppose you're asked: Show me
Hey,
it depends on what type of relation you want. I'm no expert, but
here's my 2cents.
If PEOPLE can only have one shirt, one pants, one shoes ...
then
(1)your PEOPLE table might look like.
CREATE TABLE PEOPLE(
people_id auto.. blaa
pants_idint ..
I have a relational DB question. I'll preface this and say I've had no
formal training in DB's only on-the-job knowledge. I've been trying out some
CASE tools and have discovered the following:
Lets say I have a table that stores PEOPLE. I also have a table that stores
SHIRTS, PANTS, SHOES. Now
