Please do not multi-post. How is someone reading one group supposed to be
aware of the conversation in another, except by accident? Multi-posting
is
very bad practice. If you must reach multiple groups, rarely very
helpful,
you can cross-post instead.
Eric Kaplan wrote:
> I have a group of TV listing data need to map into database tables.
>
> Data looks like following:
> http://www.oniva.com/upload/1356/crew.jpg
>
> I want to create a table for productionCrew of each TV program
>
> the data is like -
> crew -> programID -> member
> -> member
> -> member ... etc
> -> programID -> member
> -> member
> -> member ... etc
> -> programID -> member
> -> member
> -> member ... etc
> ... etc
>
> above are data from productionCrew of all TV program, for each
> programID we have a list of members.
>
> Should I merge all member into a big string?
I don't know what you mean by that question, but the answer is no.
> Or should I use 2 tables to store the Crew data?
If Crew data were the only things you saved, one might do, but you're also
storing member data and program data, right?
You need at least three tables.
Study up on database normalization and third-normal form. This will clear
up
the matter.
> If i use 2 tables, how the fields / column will look like?
What are the attributes of the real-world things your database will model?
--
Lew
|
