Re: How can I easily and effectively support (language) translation of column values?

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: How can I easily and effectively support (language) translation of column values?
Date: 2007-10-28 00:37:55
Message-ID: 20071028003754.GG4423@merkur.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Oct 28, 2007 at 01:59:22AM +0200, Dennis Brakhane wrote:

> I have some problems supporting "translatable columns" in a way that
> is both efficient and comfortable for the programmer who has to write
> SQL-Queries (we use iBatis)

Maybe this helps a bit:

http://salaam.homeunix.com/~ncq/gnumed/schema/gnumed-schema.html

Look at the tables und functions under the i18n schema.
Basically it provides a _() reimplementation in SQL, so

select
_(translatable_column) as translated_column
from
table_with_translatable_columns
...

works as expected. Which language to translate to is set in
another table which is evaluated by the _() function at
runtime.

You could evaluate that table from a view base on
current_user() if you don't want to write 50+ views for the
different languages.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-10-28 03:39:05 Re: Fragments in tsearch2 headline
Previous Message Dennis Brakhane 2007-10-27 23:59:22 How can I easily and effectively support (language) translation of column values?