It's just theory right now, but it does allow for better sandboxing to keep everyone's data in different data stores.
I am not sure how one might add / remove repositories at runtime. It might require a restart of the app when a new repo is added. Any ideas on dynamic repositories while running? That may not be threadsafe? On Aug 10, 12:15 am, Thanatos <[email protected]> wrote: > May be possible, but certainly not recommended. Just out of an > architectural curiosity: why a data-store per user? That seems like a > giant red flag to me. > > For informational > purposes:http://datamapper.org/doku.php?id=getting_started_with_datamapper&s[]=datamapper&s[]=setup > Notice how a symbol is passed in, that can be a unique identifier > associated with a user. A string username symbolized or something like > that. > > On Aug 8, 3:59 pm, myobie <[email protected]> wrote: > > > > > Is it possible to create repositories on an ad-hoc basis? I have a > > project where each user will have a data store, so each model will > > need to be able to change it's repository url based on which user it > > belongs to. Is that even possible? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
