I guess I'd add a table of languages for each entry, but it
on the project, since this approach has a seek time penalty.
"Production Monkey" <firstname.lastname@example.org>
wrote in message
> I'm designing a database for a multilingual project and
I see a couple
> different ways of approaching the problem.
> 1. I can have different colums for each language, let's
say English and
> French. I.e.
> 2. I can keep the colum names the same and use seperate
tables for each
> language. I.e.
> There are pros and cons for either approach. I'm curious
if anyone has
> with this and would be generous to relate their