Nope, your way is the better way :)
On Friday, March 9, 2012 8:14:57 AM UTC+8, Derek wrote: > > Let's say I am designing a database. > > It has these elements: > Companies, Locations, Servers > > Each company has one location, and one or more servers. > Each server has one and only one location. > > So, company "Telefónica de España" has location "Madrid". > They have four servers, "Pablo", "Alejandro", "Guido", and "Franco". > > There are three locations in the database: > Madrid (Spain), Paris (France), and Riccone (Italy). Obviously, Pablo and > Alejandro are in Spain, Guido is in Italy, and Franco is in France. > > So, I want it so that if I change the name of the location (such as > changing 'Madrid' to 'al-Mudaina') it will be updated on both the > companies and servers. > > To set this up, do I need to have two extra tables "location to server" > and "location to company" or is there a better way to do it? > > >
