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 larry.meadors@gmail.com
 designates 66.249.92.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=V3Wgqy4ZKsq4bN1r/NDS157hcWCkZE5zqt1JJ9pSRZIot7PdO8hdr6bDg11ImdLDXZ+a5YZtwqSmtCiljFHGtdHh97RHfAKIR2IEXBOfiy23ZN+9swOruaiBWiLoE4P7fWY4uHCOnea1W5Wy8CW251mGuSrzrh5oRbcYP7xXois=
Message-ID: <a10a823c0707050742y74736f54maa1db93c56e167bb@mail.gmail.com>
Date: Thu, 5 Jul 2007 08:42:04 -0600
From: "Larry Meadors" <lmeadors@apache.org>
Reply-To: lmeadors@apache.org
Sender: larry.meadors@gmail.com
To: "Collin Peters" <cadiolis@gmail.com>
Subject: Re: I18N best practices with iBatis
Cc: user-java@ibatis.apache.org
In-Reply-To: <df01c91b0707041754r42de8e10v42e708ae88663f31@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <df01c91b0706291003gf2684bfnd3239a8f95ee3d65@mail.gmail.com>
	 <a10a823c0706291837p590c0f49kf90dc874e9b150e3@mail.gmail.com>
	 <df01c91b0707041754r42de8e10v42e708ae88663f31@mail.gmail.com>

Is this a web app or a desktop app?

Larry


On 7/4/07, Collin Peters <cadiolis@gmail.com> wrote:
> On 6/29/07, Larry Meadors <lmeadors@apache.org> wrote:
> > So you have a field for each locale?
>
> Yes, a column for each locale in the i18n table
>
> > I'd think it would be easier to if that were a compound key instead:
> >
> > SELECT a.activity_id, i.name as name
> > FROM  activities a
> > JOIN  i18n i ON (a.name_i18n_id = i.i18n_id and i.i18n_locale = #locale#)
> >
> > But.. I guess you'd still have to pass it to each query...
>
> Yup, same question for iBatis
>
> > How about this - if you don't have a ton of locales to support, you
> > could do this:
> >
> > SELECT a.activity_id, i.${locale} as name
> > FROM  activities a
> > JOIN  i18n i ON (a.name_i18n_id = i.i18n_id)
> >
> > Then pass in the locale when you create the sqlmap client - each
> > locale would have it's own sql map client that you could put in a Map,
> > then put on the thread (use a ThreadLocale) and get from there when
> > needed. That could be a pretty clean solution if done well.
>
> Can you expand on this idea a bit?  I'm not sure what you mean with
> the Thread idea.  In the end all I want is a way to abstract having to
> send the locale as a variable to *every* single call in my iBatis
> code.
>