0

The project I am working on has a lot of dependency on foreign languages. In order to capture all required content in foreign languages I have designed the following DB diagram.

enter image description here

Since I want to address the issue of scalabilty at early stage of DB design, I want to know is this a good way to go? An alternative solution would for each table Products, Agents (and any futher tables) to have its own content/content languages table such as ProductsContent, ProductsContentLanguages, AgentsContent, AgentsContentLanguages.

Splitting and duplicating table structure would shrink table size, and would improve performance, especially since each table would not contain equal number of entries. I believe the difference would be more then obvious when tables get very large.

So what would be a good database design in this particular case?

mko
  • 6,638
  • 12
  • 67
  • 118

1 Answers1

0

Here are some tips and links that maybe useful for your current scenario,

"Multilanguage Database Design in MySQL"

What are best practices for multi-language database design?

What is the best database design for multi-language data?

Community
  • 1
  • 1
WiredTheories
  • 231
  • 7
  • 18