Earle, Great glad to hear someone has tried this before. If you have time I'd like to hear some of your thoughts/advice on the experience. If you have developed any patterns/code that you could share.
I have started with AR and it looks possible--but maybe you ran into a wall--or I just haven't yet! On Feb 10, 6:09 am, Earle Clubb <ecl...@valcom.com> wrote: > On Mon, Feb 9, 2009 at 11:44 PM, Corbin <corbinhoe...@gmail.com> wrote: > > > Is anyone using datamapper in a production app to access multiple > > databases? I am looking at building an application that allows each > > client to have their own database with the same schema. Everything I > > am reading about ActiveRecord makes this look like a total hack. > > > I also need to build a new client database at runtime when a client > > creates an account. I started building rake tasks to do this with > > normal active record migrations....is this possible with datamapper I > > am little fuzzy on what tools dm has for migrations/database > > management. > > Corbin, > > I'm doing something very similar. I actually switched to from AR to DM > precisely because of how easily DM handles multiple databases (and its > inherent thread safety). In my scenario, I have a blank database with my > default schema. When I need a new copy, I just copy the default database > and open a connection to it using a unique context. Whenever I want to > access that database, I just wrap the access in a repository block. I'm > using SQLite3. > > Earle --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to datamapper@googlegroups.com To unsubscribe from this group, send email to datamapper+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
