| Description |
For each language an extra language-dependent column is created. The language-dependent columns must have the same format as the native columns. |
A host table is created with all predefined columns. A new table is created for each language. The table contains the primary key(s) of the host table and the columns to localize. |
A host table is created with non-localizable columns. A new table is created with the host tables’s primary key, language code, and localizable data. |
The database file is cloned and the localizable data of the cloned database file is replaced with translations in Multilizer project. |
| Change database's structure |
Use the database vendor’s administration tool to add the language-specific columns. |
Use the database vendor’s administration tool to add the language-specific tables. |
Use the database vendor’s administration tool to create tables for localizable data. |
Not required. |
| Change software's source code |
E.g., Change SQL clause
SELECT Id, Description FROM Table;
to
SELECT Id, Description_DE FROM Table;
where column Description_XX contains the localized data in selected language. |
E.g., Change SQL clause
SELECT Id, Description FROM Table;
to
SELECT Table.Id, Table_DE. Description FROM Table, Table_DE WHERE Table.Id = Table_DE.Id;
where table TABLE_XX contains the localized data in selected language. |
E.g., Change SQL clause
SELECT Id, Description FROM Table;
to
SELECT Table.Id, Table_DATA. Description FROM Table, Table_DATA WHERE Table.Id = Table_DATA.Id AND Table_DATA.Lang LIKE 'FI';
where value of Table_DATA. Lang contains the language code of localized data. |
E.g. Change connection string
DRIVER = Microsoft Access Driver (*.mdb); DBQ = products.mdb;
to
DRIVER = Microsoft Access Driver (*.mdb); DBQ = products_DE.mdb;
where database products_XX. mdb contains the localized data in selected language. |
| Overview |
+ Simple to implement. |
+ Can be implemented in on-line systems.
+ Possible to isolate the localizable data in separate tables. |
+ Possible to isolate the localizable data in separate tables.
+ Recommended way of database localization for Oracle® 9i. |
+ Very simple to implement. |
| Database-specific |
+- Requires changes in existing tables.
- Might consume a lot of space. |
+ Doesn't require changes in existing tables.
+- Each new language requires new tables for each native table. |
+- Requires changes in existing tables.
+ Optimizes space usage.
+ No duplicated data. |
- Supported in single-file databases only.
+- Requires frequent data synchronization. |
