Re: sakila database design question
My take would be that there is usually a 1:1 relationship between customer and street address, so those bits of info go in one table, but 1:M between customer and city, so city gets it own table, with a key from the customer table. Then, if the zip code for a city changes, you only need to update 1 row in the city table, not the row of every customer in that city.
Good luck,
Barry.
Subject
Written By
Posted
September 29, 2015 07:49AM
September 29, 2015 11:42AM
September 29, 2015 08:17PM
Re: sakila database design question
September 29, 2015 08:34PM
September 29, 2015 11:47PM
September 30, 2015 06:12AM
September 29, 2015 12:16PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.