Yes, and yes. That sounds fine.
Just be careful not to optimise prematurely (ie... make design decisions with a VIEW to the future, but don't let that both you too much in the present). Chances are when it comes to architecture and optimisation, Ya Aint Gonna Need It, and when you do, it'll most likely be different than you think it will be now. Focus more on the classes in your system than how to efficiently store them at the inception/design stage. Julian On 04/04/2013, at 5:29 PM, Johan Vauhkonen <johan.vauhko...@gmail.com> wrote: > Is it possible to dynamically create new databases and tables within them > with Rails? > > Or is that a task best done manually? > > I'm creating an application which should allow users to store their own > statistics information (which can and probably with time will be a lot). > My initial thought was to give each user their own database to keep their > data separate from each other due to the possible large quantity of data each > user will have. > > Good idea? Bad idea? Other ways to do it? > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-talk+unsubscr...@googlegroups.com. > To post to this group, send email to rubyonrails-talk@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-talk/-/ZRLrcnKJ-fsJ. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
