dbTalk Databases Forums  

Table Schema

comp.databases.oracle.misc comp.databases.oracle.misc


Discuss Table Schema in the comp.databases.oracle.misc forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Ana C. Dent
 
Posts: n/a

Default Re: Table Schema - 03-23-2008 , 10:14 PM






Eric Kaplan <tobycraftse (AT) yahoo (DOT) com> wrote in
news:srbeu3tj8lpgkat30icrkr4d8bp8c94hju (AT) 4ax (DOT) com:

Quote:
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?
Or should I use 2 tables to store the Crew data?

If i use 2 tables, how the fields / column will look like?
The data should be placed in Third Normal Form


Reply With Quote
  #2  
Old   
Ana C. Dent
 
Posts: n/a

Default Re: Table Schema - 03-23-2008 , 10:14 PM






Eric Kaplan <tobycraftse (AT) yahoo (DOT) com> wrote in
news:srbeu3tj8lpgkat30icrkr4d8bp8c94hju (AT) 4ax (DOT) com:

Quote:
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?
Or should I use 2 tables to store the Crew data?

If i use 2 tables, how the fields / column will look like?
The data should be placed in Third Normal Form


Reply With Quote
  #3  
Old   
Ana C. Dent
 
Posts: n/a

Default Re: Table Schema - 03-23-2008 , 10:14 PM



Eric Kaplan <tobycraftse (AT) yahoo (DOT) com> wrote in
news:srbeu3tj8lpgkat30icrkr4d8bp8c94hju (AT) 4ax (DOT) com:

Quote:
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?
Or should I use 2 tables to store the Crew data?

If i use 2 tables, how the fields / column will look like?
The data should be placed in Third Normal Form


Reply With Quote
  #4  
Old   
Ana C. Dent
 
Posts: n/a

Default Re: Table Schema - 03-23-2008 , 10:14 PM



Eric Kaplan <tobycraftse (AT) yahoo (DOT) com> wrote in
news:srbeu3tj8lpgkat30icrkr4d8bp8c94hju (AT) 4ax (DOT) com:

Quote:
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?
Or should I use 2 tables to store the Crew data?

If i use 2 tables, how the fields / column will look like?
The data should be placed in Third Normal Form


Reply With Quote
  #5  
Old   
Eric Kaplan
 
Posts: n/a

Default Table Schema - 03-23-2008 , 10:35 PM



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?
Or should I use 2 tables to store the Crew data?

If i use 2 tables, how the fields / column will look like?

Reply With Quote
  #6  
Old   
Eric Kaplan
 
Posts: n/a

Default Re: Table Schema - 03-23-2008 , 11:43 PM



How to organize the fields in Third Normal Form give the following
data?
http://www.oniva.com/upload/1356/crew.jpg
============================
crew -> programID -> member
-> member
-> member ... etc
-> programID -> member
-> member
-> member ... etc
-> programID -> member
-> member
-> member ... etc
... etc
============================
Each member -> role + first name + last name


Quote:
The data should be placed in Third Normal Form

Reply With Quote
  #7  
Old   
Eric Kaplan
 
Posts: n/a

Default Re: Table Schema - 03-23-2008 , 11:43 PM



How to organize the fields in Third Normal Form give the following
data?
http://www.oniva.com/upload/1356/crew.jpg
============================
crew -> programID -> member
-> member
-> member ... etc
-> programID -> member
-> member
-> member ... etc
-> programID -> member
-> member
-> member ... etc
... etc
============================
Each member -> role + first name + last name


Quote:
The data should be placed in Third Normal Form

Reply With Quote
  #8  
Old   
Eric Kaplan
 
Posts: n/a

Default Re: Table Schema - 03-23-2008 , 11:43 PM



How to organize the fields in Third Normal Form give the following
data?
http://www.oniva.com/upload/1356/crew.jpg
============================
crew -> programID -> member
-> member
-> member ... etc
-> programID -> member
-> member
-> member ... etc
-> programID -> member
-> member
-> member ... etc
... etc
============================
Each member -> role + first name + last name


Quote:
The data should be placed in Third Normal Form

Reply With Quote
  #9  
Old   
Eric Kaplan
 
Posts: n/a

Default Re: Table Schema - 03-23-2008 , 11:43 PM



How to organize the fields in Third Normal Form give the following
data?
http://www.oniva.com/upload/1356/crew.jpg
============================
crew -> programID -> member
-> member
-> member ... etc
-> programID -> member
-> member
-> member ... etc
-> programID -> member
-> member
-> member ... etc
... etc
============================
Each member -> role + first name + last name


Quote:
The data should be placed in Third Normal Form

Reply With Quote
  #10  
Old   
fitzjarrell@cox.net
 
Posts: n/a

Default Re: Table Schema - 03-24-2008 , 07:29 AM



On Mar 24, 12:43*am, Eric Kaplan <tobycraf... (AT) yahoo (DOT) com> wrote:
Quote:
How to organize the fields in Third Normal Form give the following
data?http://www.oniva.com/upload/1356/crew.jpg
============================
crew -> programID -> member
* * * * * * * * * * * * * * * *-> member
* * * * * * * * * * * * * * * *-> member .... etc
* * * * *-> programID *-> member
* * * * * * * * * * * * * * * *-> member
* * * * * * * * * * * * * * * *-> member .... etc
* * * * *-> programID *-> member
* * * * * * * * * * * * * * * *-> member
* * * * * * * * * * * * * * * *-> member .... etc
* * * * * ... etc
============================
Each member -> role + first name + last name



The data should be placed in Third Normal Form- Hide quoted text -

- Show quoted text -
Apparently you don't fully understand the nature of your data. Each
program has a cast/crew, but members of one program's cast/crew could
also be working on, or have worked on, any number of other programs.
Possibly you should start with the people (cast/crew) and build a
table for that data (for example CAST_CREW), assigning a CAST_ID to
each person, which would be unique. Then you could build a table of
your programs (TV_PROGRAMS), associating the relevant CAST_IDs to
each. The role played would be contained in the table of program
data, rather than being associated with the actor in the cast_crew
table.

I won't do any more for you as this appears to be homework. However,
if you get confused, post what you have designed here and you'll
likely get helpful pointers.


David Fitzjarrell


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.