2009/9/3 JL Smith <autige...@gmail.com>: > > Incompatible with production DB? Rails/ActiveRecord is database > independent (as long as you aren't using proprietary functions in raw > SQL queries). The code you wrote in development against a SQLite > database will work with MySQL, Oracle, Postgresql, etc. in production > with simply a change to database.yml. That's one of the biggest > selling points of Rails.
Personally I am uncomfortable with using different db servers in the different environments, particularly between test and production. I like the test environment to be as similar to production as feasible. Colin > > Since SQLite is "serverless", it's the easiest to get up and running > for development. I'm sure that's why Rails defaults to SQLite. But > hardly anyone recommends SQLite for production, obviously. > > > On Sep 3, 12:04 am, Marnen Laibow-Koser <rails-mailing-l...@andreas- > s.net> wrote: >> Lee Smith wrote: >> > I guess I didn't clarify that...I'm simply saying that I use SQLite >> > for development because it's so lightweight and easy to setup. >> >> I figured that. But what good is it if its syntax is incompatible with >> that of your production DB? >> >> > The >> > firefox plugin is icing on the cake. >> >> And pretty interesting icing. >> >> Best, >> -- >> Marnen Laibow-Koserhttp://www.marnen.org >> mar...@marnen.org >> >> -- >> 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
