Timeline for Tables with FK's of each other
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 18, 2016 at 15:31 | comment | added | ypercubeᵀᴹ | @Krowi which suggestion did you follow? In my answer there, I have several, the first one being identical to this answer. | |
| Sep 28, 2015 at 10:19 | vote | accept | Krowi | ||
| Sep 28, 2015 at 10:19 | |||||
| Sep 21, 2015 at 19:15 | comment | added | TommCatt | The main benefit is that it is impossible to designate more than one city as the capital of a country. As you gain experience with databases, you will find Murphy's Law is right at home there: if something is possible, it will happen. So you have to write trigger and/or sp code to constantly check to see if a city is being made the capital of a country and if so that there is no other city already so designated. The best you can hope for, btw, is to reduce the probability, you can never entirely eliminate it. So you also have to put in place a procedure for correcting it when it happens. | |
| Sep 21, 2015 at 8:57 | comment | added | Krowi |
Thank you for your answer. Right now I applied the approach given by ypercube's comment (dba.stackexchange.com/questions/34151/…). What benefit does your approach have by extracting the CountryCode from the City table and adding a 2nd table to link a country and a city? (New to database design.)
|
|
| Sep 21, 2015 at 7:47 | history | answered | TommCatt | CC BY-SA 3.0 |