On Dec 1, 11:30 am, "David Pollak" <[email protected]> wrote: > Lift has built in DB sharding. You can have multiple RDBMS connection > identifiers. Each record has its connection identifier associated with it > (where it came from) and there's a place in each MetaModel to insert a > function to calculate the connection identifier given a record to be saved > or a primary key to be recalled.
Revisiting this question from a few weeks ago. Very interesting to hear that Lift has thought of this ahead of time. Had to work through the ToDo tutorial to learn a little more Lift before posting. Is the idea to put something in net.liftweb.mapper.DefaultConnectionIdentifier to handle the sharding for me? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
