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.
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 > [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 -~----------~----~----~----~------~----~------~--~---
