Quote Originally Posted by bigduke
2. Imagine a thousand products with their information stored in 10 languages, thats 10,000 records spread over various tables, isn't that adding unnecessary overhead to it, not to mention the data redundancy even if it isn't the same language. So its a tradeoff now, db overhead vs. interface overhead.
That's exactly what my approach tries to resolve. The common data remains in the original table(s), only the multilingual data (like, say, product description) is stored separately. The whole thing has nothing to do with interface at all (or I might be misunderstanding what you're saying).

How would you store the data where same thing is described in several languages into a database?