If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > General > Database Concepts & Design > Need your advise: Table structure for storing information in different languages

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-14-06, 06:58
iimuhin iimuhin is offline
Registered User
 
Join Date: Jul 2006
Posts: 1
Need your advise: Table structure for storing information in different languages

Hi all,

I will develope an application that have data dictionaries translated to some languages.

Example of a non-localized table "Thing": thing_id, code, hidden, shortname, longname
Target: shortname and longname must be represented in many languages

My variants of the solution:

Model variant 1 (one table with many columns):
"Thing" table: thing_id, code, hidden, shortname_en, longname_en, shortname_de, longname_de, shortname_ru, longname_ru

Model variant 2 (two tables with default language in the parent table):
"Thing" table in english: thing_id, code, hidden, shortname, longname
"Thing_Loca" tabl: thing_id, locale, shortname, longname

Model variant 3 (two tables with language data in the child table):
"Thing" table: thing_id, code, hidden
"Thing_Loca" tabl: thing_id, locale, shortname, longname


My questions:
1) Do you know about any other models?
2) Which model would you prefer?
3) Do you konw any internet resources about this problem?

Thanks for your answers
Igor
Reply With Quote
  #2 (permalink)  
Old 07-16-06, 03:32
gannet gannet is offline
Registered User
 
Join Date: Oct 2002
Location: Plymouth UK
Posts: 116
I think here you need to look at how easy it would be to add another language version to your system. Variant 1 would entail adding more fields to your table. Variants 2 & 3 require no structural changes to the database, just the additional of data. Personally I would favour Variant 3.

Also you might want to consider adding another table for locale info, which you foreign key link to in your thing_loca table. Depends on whether you want further info on the language in question, eg. dialects, versions of a language (UK english, US english).
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On