Timeline for Create a column mostly with null data SQL like
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2019 at 6:20 | vote | accept | Accollativo | ||
| Sep 16, 2019 at 6:20 | |||||
| Sep 14, 2019 at 18:35 | comment | added | Doc Brown | @Accollativo: the problem with the "one table" approach is, when your program evolves and you will have to add new columns to a city which are independent from the translation (for example, number of inhabitants, area, or something like that), the same columns will automatically be introduced into the translation records. You end up having two places where this information could be stored, which has some risk of introducing errors or inconsistencies. | |
| Sep 13, 2019 at 18:45 | answer | added | Jon Raynor | timeline score: 8 | |
| Sep 13, 2019 at 13:13 | comment | added | Accollativo | @BartvanIngenSchenau same CITY_ID, different LANGUAGE. The combination of both will be the new primary key. | |
| Sep 13, 2019 at 12:29 | comment | added | Bart van Ingen Schenau | If there are more properties stored in this table, how would the software know that "Rome" and "Roma" refer to the same city and that an update needs to be applied to both rows? | |
| Sep 13, 2019 at 10:48 | comment | added | Accollativo | I will duplicate the row, for example the city of "Rome" will have a row with LANGUAGE "ITA" and the CITY_NAME="Roma" and another row with "ENG" and the CITY_NAME="Rome" | |
| Sep 13, 2019 at 10:22 | answer | added | Bohdan Stupak | timeline score: 1 | |
| Sep 13, 2019 at 10:15 | comment | added | Bohdan Stupak | "only one table .. and a new column LANGUAGE that wil be "ENG" or "ITA"" - what if the city will have both names in English and Italian? | |
| Sep 13, 2019 at 10:13 | comment | added | Accollativo | No, but the solution is pretty similar. I think to keep only one table, with a column CITY_NAME (that can be in english or other language) and a new column LANGUAGE that wil be "ENG" or "ITA". This solution would be nearly equal to what you propose, to create a new table with CITY_ID, CITY_NAME and LANGUAGE, I suppose there is no real advantage in it. | |
| Sep 13, 2019 at 10:04 | comment | added | Bohdan Stupak | Am I correct that in the second approach you want to add the table with city name English localization? | |
| Sep 13, 2019 at 9:59 | comment | added | Accollativo | @BohdanStupak you've right, I edited the post. | |
| Sep 13, 2019 at 9:59 | history | edited | Accollativo | CC BY-SA 4.0 |
added 3 characters in body
|
| Sep 13, 2019 at 9:58 | comment | added | Bohdan Stupak | "Add a new row CITY_NAME_ENG" - are you sure you're not confusing rows and columns? | |
| Sep 13, 2019 at 9:44 | comment | added | Accollativo | Good question. I suppose we will not add another language (surely not for the next 3 years). | |
| Sep 13, 2019 at 9:18 | comment | added | Robert Harvey | How likely is it that you will add another language later, and then another? | |
| Sep 13, 2019 at 9:10 | review | Close votes | |||
| Sep 18, 2019 at 3:05 | |||||
| Sep 13, 2019 at 8:52 | history | asked | Accollativo | CC BY-SA 4.0 |