Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (herse.apache.org: domain of cadiolis@gmail.com designates
 64.233.162.230 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=bFNjKSb8Fu+QXFpUdQTpkG2zYbHlJVNkAbbyVAdAzIyezPSM1md8HAyho8JX/CCQTF4iPrywU2h5KzYCx42ltdkZzsUKpoLXwMhps73CaKTA3M5UpISGQUIYifnkK65veeQ3eke62GhXNqEAtEMsLym55Vzve1/LS9XADu6ukLA=
Message-ID: <df01c91b0706291003gf2684bfnd3239a8f95ee3d65@mail.gmail.com>
Date: Fri, 29 Jun 2007 10:03:39 -0700
From: "Collin Peters" <cadiolis@gmail.com>
To: user-java@ibatis.apache.org
Subject: I18N best practices with iBatis
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I have some I18N questions and am wondering what others do out there.

We have an I18N system setup where there is a database table storing
all strings and their translations.  There is tags against each i18n
string and then they will get written out different files (some
.properties for java, some .xml for flash/flex, some .php for php
etc...).  We also do some queries where we do a join against this
table to keep things simple at the database level.  How this looks is:

SELECT a.activity_id, i."en_US" as name
FROM  activities a
JOIN  i18n i ON (a.name_i18n_id = i.i18n_id)

This means that we have to pass in the locale (en_US) to the query.
In PHP, Perl, and straight Java this isn't a problem.  But how would
this easily be accomplished with iBatis?  Do I have to pass in the
locale as a parameter to *every* query that supports it?  Would there
be some way of making this automatic and transparent?

Regards,
Collin Peters