I appreciate your replys, I will look into PostgreSQL a little futher. A post from yesterday indicated alot of success with PostgreSQL, so I will probably go with it. One other thing..
I'm pretty new to rails, and this question may seem ridiculous, but I must ask. If I keep my fields the same in my migration, and simply change my database.yml file will my views and controllers still work fine? I haven't done alot of development on this app yet, but anytime I can avoid rewriting code it's nice. Thanks! Chris On Apr 18, 12:52 pm, Marnen Laibow-Koser <rails-mailing-l...@andreas- s.net> wrote: > internetchris wrote: > > [...] > > > In essence I don't want my > > rails application to be limited by database capability or size. > > I would think that it would be better to have the DB take care of the > multi-DB splitting, and have it appear to the Rails app as one DB. > > > As I > > said before I have never designed an app like this, and I want to get > > it right before I get too far into the application. I have just > > started the coding, and would like to be proactive on making the right > > decision. > > The right decision would almost certainly *not* be to use mySQL. > PostgreSQL is generally more capable and faster. It's also more > extensible. > > > > > Thanks! > > > Chris > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > [email protected] > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
