[UPHPU] Database Speed Question

[Jennifer Charrey]

If you're only really worried about the US rating for each movie,  
then just do:

Movies Table
	Movie_ID
	Movie_Title
	Movie_Year_Released
	Rating_Code

Rating Description Table
	Rating_Code
	Rating_Description

If by Rating_Description you mean "Parental guidance suggested" or  
something like that then neither of your original schema are properly  
normalized because you'd be repeating that data thousands or millions  
of times.

If you start worrying about other countries you're going to have a  
lot of other issues too, like where other countries use a different  
title, or the movie is released in a different year. If you can  
simplify the problem to just include US info until your service  
really is poised for international popularity, you'll make a lot  
faster progress. See "pre-optimization."

..........................
Jennifer Charrey
jcharrey at xmtp.net


On Apr 11, 2007, at 2:33 PM, Webot Graphics wrote:

>> I say if there is any chance that a movie could have more than one
>> rating (let's say a year or two down the road you change your mind),
>> go with the normal(ized) way with relational tables.  If there is no
>> chance at all there will be any more than one rating per movie, go
>> with the first option.
>
> There is the possibility that the movie could have more than one  
> rating, but it would be from another country or something that  
> would probably need its own table anyways.
>
> Other than that I don't think that the movie could really have more  
> than one rating. Anyone have another opinion?
>
> Justin Giboney
> www.forodeherbales.com
>
>
>
> _______________________________________________
>
> UPHPU mailing list
> UPHPU at uphpu.org
> http://uphpu.org/mailman/listinfo/uphpu
> IRC: #uphpu on irc.freenode.net