Skip to content

Translations in the database #190

Description

@racke

For tables carrying fields which are subject to translations, I propose the following way to introduce i18n:

We add a xxx_i18n table, e.g. for products it would contain:

primary key
sku
language_iso_code
name
short_description
description
uri
created
last_modified
active
author_users_id

Feedback would be appreciated.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions