yeah that's the approach i've already decided to take, as with it being 3
tables, it's the lowest table count i could come up with when brainstorming a
few different ways of doing it... thanks for confirming it tho :)
wavewave
Richard Lindsey.
-----Original Message-----
From: Cameron [mailto:[EMAIL PROTECTED]
Sent: Mon 8/23/2004 1:59 PM
To: Richard Lindsey; [email protected]
Cc:
Subject: RE: MySQL...
"is there a better suggestion out there for what I'm trying to do,
besides
making 3 tables, one to hold mob_index_data with a primary key of vnum,
one
for mprog_data with a primary key of vnum, and one to hold
mob_mprog_associations with foreign keys for both vnums, for this
scenario?
Do I even have that straight in my head? Any help would be appreciated
:D"
This solution is the "proper" way to do it. With your proposed 3 table
system you will end up with properly normalized tables. I'd say it's
the
best bet...
Cameron
