Skip to content
This repository was archived by the owner on May 28, 2026. It is now read-only.
This repository was archived by the owner on May 28, 2026. It is now read-only.

Util.Texts not really Multilingual #8

Description

@alxdean

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions