All of our localised data is saved in resource files.
NHibernate is completely free of any "localised" data. On , xtoff <[email protected]> wrote:
Hi,
I was wondering how other people are handling localisation (l10n) when
dealing with NHibernate.
I'm jumping onboard a project that builds an app that is doing it by
having two sets of tables for pretty much every entity, say Customer
and Customer_l10n where Customer table holds customer information
(name, dob, stuff that is not to be translated) and Customer_l10n
holds stuff that is going to be language dependent, like say string
"First name" in multiple languages, display values for things like
customer status "normal", "gold", "platinum" etc.
Then every query does stuff like "select * from Customer c where c.Id
= :bla" and also "select * from Customer_l10n l where l.LanguageCode
= :bla".
I'm pretty sure there are also cases where there's actual join between
those tables, but I haven't seen the codebase yet so I don't know what
those cases actually are.
So my question is - how do you guys handle those concerns. I'm sure
many of you have l10n in your apps.
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
-- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
