That seems reasonable, although IIRC it means that you need two queries to the database to fetch a translation using mapper strictly. Of course, you could use the raw SQL queries on DB to fetch things with one join.
Derek On Sun, Mar 1, 2009 at 2:54 PM, Tim Perrett <[email protected]> wrote: > > Guys, > > Just working something through and would like a bit of input from > lifted :-) > > Im debating how im going to store my locale data and present that > information to the user in a sensible way. Right now, im thinking of > using MappedLocale to hold locale type information in my database, and > then have a one-to-many (locale -> translation). This seems fairly > reasonable, but i've changed my mind several times now so would be > ever so grateful for some other input :-) > > Cheers, Tim > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
