All we need is an easy explanation of the problem, so here it is.
I am trying to design TVGuide database
as you can see one TV program can have many shows, as well as one show can play on multiple tv programes
this is all going fine
The problem I am trying to solve is what to do when show is on multiple dates, for example a movie is on BBC 1 at 04/04/2012 and then they play it again at 08/08/2012 right now I would have duplicate movies with different dates, is it possible to reduce this somehow, so I would have one movie with many dates or (a movie can also be played only once) something like that
Thanks for Anwsering and Best Regards
BTW: I am using Toad data modeler 6.5 to design this db in and here is its design: https://www.mediafire.com/file/lek90uvy8pz9wr8/TVGuide.txp/file
How to solve :
I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.
Method 1
In similar vein to what mustaccio is getting at in the comments, I’d make another table called something along the lines of TV_Schedule. It could have the columns (TV_Schedule_ID, TV_Show_TV_Station_ID, Airtime_Start, Airtime_End) and would be a child table that’s foreign key related to TV_Show_TV_Station by the column TV_Show_TV_Station_ID. This would be a one-to-many relationship.
This way you wouldn’t manage the presentations in the TV_Show table, causing unneeded duplicate data.
Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0