Re: Multilingual table design questions
Date: Mon, 20 Feb 2006 15:52:49 +0200
Message-ID: <dtchjj$jk7$1_at_nntp.aioe.org>
"Murdoc" <murdoc_0_at_hotmail.com> wrote in message
news:xn0eippie1uf6t001_at_news-south.connect.com.au...
> Guy wrote:
> > Anybody has a better approach?
> Personally, I believe translation is purely a presentation function,
rather than a data/business
> function. I would store the text in whatever language you want as a base
level (English, probably),
> then when displaying the text, translate it. This cuts down on the
database size, and leaves all
> the translation in the Presentation layer. Also, your database schema does
not need to change every
> time a new language becomes supported.
>
> I'm not sure how your UI is implemented, though, so I am unable to give
specifics for your
> implementation.
I agree with this solution.
Other solution would be implementing Name as a user defined type if your
DBMS support it.
Then implement the operators to get the french, english or whatever
translation you want.
Received on Mon Feb 20 2006 - 14:52:49 CET