Comments on: Multilanguage database design approach

By: Internationalization with Entity Framework Code First – Part I « Luís Gonçalves

Thu, 11 Aug 2011 22:59:19 +0000

[...] on a web application that uses EF Code First. When deciding the data model to use I came across this post, which describes 4 possible approaches. We needed the model to easily support adding new languages, [...]

By: gabi solomon

gabi solomon — Fri, 22 Jul 2011 08:11:00 +0000

that is true of the single table aproach that is whyi dont use it

By: Dat Nguyen

Dat Nguyen — Fri, 22 Jul 2011 04:42:00 +0000

Hi, I found your article is very helpful.

But the one problem I see that is all translations for all languages will be stored in one table. That is easy to maintain but cannot handle the large data, especially when you are using MySQL.
For example, my table has more than 250.000 records, I have 22 languages, so the translation table will have 250.000 * 22 = 5.500.000 records. Will that cause the query slows down?

Dat

By: Multilanguage DB, check approach - dBforums

Multilanguage DB, check approach - dBforums — Wed, 08 Jun 2011 17:59:37 +0000

[...] Im looking for ways to design multilanguage db. So far, my solutions war like on this link: Multilanguage database design approach | GS Design but the first two are to simple. I need some ideas of designing besides these on the link, if u [...]

By: Haq Voice

Haq Voice — Mon, 21 Mar 2011 19:17:00 +0000

all option are very helpful but 2 very important things are missing in advantage or disadvantage column,
1. while entering data, how to manage each language, especially deleting and re-entering

2. while displaying data, switching language and maintaining same page

By: Qtronik

Qtronik — Fri, 14 Jan 2011 17:46:00 +0000

Really nice and clean thé finnaly information I searched for a loooong time ! Tanks ! Had you made a class for it ?

By: Qtronik

Qtronik — Fri, 24 Dec 2010 05:26:52 +0000

I simply use onetable for each Lang
Ex: lang_en table, lang_fr table (id, page_id, chunk_id)

with a table for language (id and isoname row)
and a table for pages (id, pages_name)

When I call a array for all chunk of a page I call the query with the user default or set lang isoname for theright lang-table... No "join"... to slow for quering.

and after one time the user show a page I put an cache for not quering again for recurent chunk translate like the menu !

By: Mpmskwa

Mpmskwa — Sat, 25 Sep 2010 16:49:08 +0000

I NEED TO IT TOO FRIEND

By: Bernard

Bernard — Tue, 17 Aug 2010 15:25:21 +0000

I wrote 'variabes' , i ment 'tables'

fe:
FAQS
faq_id
lang_id
node_id
you could create 100 tables this way and store everything in 1 table as benieve
(just to illustrate, have no id if this is the right setup) but building it this way would lead to much easier sql queries i believe

table nodes
node_id (ai)
lang_id
node_id
content

By: Bernard

Bernard — Tue, 17 Aug 2010 15:19:10 +0000

I came to the same setup as yours, if only i found this artice a bit sooner it would have save me some headtroubles…the disadvantage is there !! this setup leads too a huge amount of 'translation' tables…

so now i'm thinking if it wouldn't be much easier to create a 'translate node' table wich would store every entry in such a way that it would only require an id (or2) to select the right translation…
All translations would be stored in 1 table, this would need an entire editing of the standard tables but it would be much less complex ones the db is edited

I'm not sure yet how this would look like, i'm still brainstorming on this but it would solve the disadvantage of this approach and you could easily and instantly add new variables…