Country/Region/City Data Model
Country: countryID, countryNameRegion: regionID, countryID (FK), regionNameCity: cityID, regionID (FK), cityNameAll countries will have cities.Not will all countries will have regions. Region will only...
View ArticleAnswer by plague for Country/Region/City Data Model
why not have a countryID in the city table as well so you can map back to either region or country depending on your need at the time
View ArticleAnswer by Shahriar for Country/Region/City Data Model
Well,if you put regionID in you city table,and if you don't have region,it would be null in your city table too.So no benefit.You are asking about a 0-To-Many relationship which is a 1-to-many...
View ArticleAnswer by sfinnie for Country/Region/City Data Model
If:All countries will have cities.and:Not all countries will have regions.then:just put countryID and regionID within City tableis the most obvious way to model it. As you suggest, it's not a...
View ArticleAnswer by Mike Sherrill 'Cat Recall' for Country/Region/City Data Model
You have two different issues here.A database design issue (how to model city names)A user-interface design issue (how should the user enter city names)Although those two issues interact somewhat, they...
View ArticleAnswer by user11328710 for Country/Region/City Data Model
I prefer the original option: tblCountry -> tblRegion -> tblCity. If no Region exists have Region = Country add a check box to indicate Region does not exist and ignore duplicate entry. Just a...
View Article
![ONEW – KAKERA -Unmei no Piece- – EP [iTunes Plus M4A]](http://is1-ssl.mzstatic.com/image/thumb/Music221/v4/d0/fb/86/d0fb86a5-ba60-4bea-41fb-7f54c125f518/VEATP-45908.jpg/296x296bb.webp)
