You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Folks,
I wanted to test a Real World Multi Lingual setup and found that the Util.Texts Table has a major design flaw. While it provides the ISOLANGUAGE field, it is not part of the key. and the unique key is only the TextID.
in the real world the data would look like this:
TEXTID;LANGUAGE;ISOLANGUAGE;TEXT
1000000001;E;en;Notebook Basic 15
1000000001;S;es;Nota libro basico 15
so the same ID has two entries, one for each language. But your Schema won't allow for it. so effectively the fields Language and ISOLanguage are useless right now.
The text was updated successfully, but these errors were encountered:
Hi Folks,
I wanted to test a Real World Multi Lingual setup and found that the Util.Texts Table has a major design flaw. While it provides the ISOLANGUAGE field, it is not part of the key. and the unique key is only the TextID.
in the real world the data would look like this:
TEXTID;LANGUAGE;ISOLANGUAGE;TEXT
1000000001;E;en;Notebook Basic 15
1000000001;S;es;Nota libro basico 15
so the same ID has two entries, one for each language. But your Schema won't allow for it. so effectively the fields Language and ISOLanguage are useless right now.
The text was updated successfully, but these errors were encountered: