Hi Riccardo, The best practice is to actually map all those localized columns as explicit properties (Cayenne ObjAttributes), and deal with language switching in the code layer above Cayenne.
Thanks, Andrus > On Nov 1, 2023, at 4:27 AM, Riccardo De Menna <deme...@tuorlo.net> wrote: > > Hi Everyone, > > I was wondering if someone could point out a best practice on how to deal > with localized content in the db. I come from the webobjects world where I > would just flag a property in the eomodel as localizable. Then fetching from > name, email, address columns would actually take data from name_en, email_en, > address_en and such. I’m sure this must be something people have dealt with > before. > > Regards, > Riccardo De Menna