You'd have two new tables:
Category (or whatever these things really are)
categoryID number PK
name varchar2(300)
And your join table I usually concat the two names of the other tables so,
so imagining these are people here...
PersonCategory
categoryID number PK FK
personID PK FK
When someone selects kiniseology, you'd add their personid (if we're talking
people here) and the id for kiniseology to the "personcategory" table.
When you want to get people and their categories, you'd just join the two
tables
SELECT p.personid, c.name AS category
FROM person p, personcategory x, category c
WHERE p.personid = x.personid
AND x.categoryid = c.categoryid
Make sense?
----- Original Message -----
From: "daniel kessler" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, July 21, 2004 1:22 PM
Subject: Re: DB field setup
> >Seems like you need a lookup table (in case the possibilities ever
> >increase from 3 to X). Then you can either store the IDs in a
> >comma-delimited list or do another lookup table where you insert the
> >userID and the type they are. Then each user can be in multiple places.
>
> While I agree that I probably need a lookup table, I don't really
understand your suggestions. Are you suggesting a Family_Studies tables
with a set of names? And would I do an INNER JOIN to grab that information?
>
> I'm a bit new to DBs.
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
