Never been a massive fan of DB design, but I've got a fairly simple requirement for data that I'd like to implement correctly.
It's a lookup for Tube Stations, my challenge is how to manage the fact a tube station can belong to more than one line?
My normal approach, if a Tube station had only one line would be to use a foreign key to join two tables. Do I need a third table that simply manages the relationship between tube station and line(s)
Thanks
It's a lookup for Tube Stations, my challenge is how to manage the fact a tube station can belong to more than one line?
My normal approach, if a Tube station had only one line would be to use a foreign key to join two tables. Do I need a third table that simply manages the relationship between tube station and line(s)
Thanks