Lee S. wrote:
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.
That’s true, of course. And I’ve used PostgreSQL for dev with mySQL in
production. However, I was under the impression that SQLite simply had
no equivalent for a lot of fairly common PG or mySQL tasks. I was also
under the impression that if you need, say, a custom :conditions string,
SQLite’s syntax is likely to be different from the other two. I could
In any case, it’s kind of a moot point for me, at least on my major
project ( http://quorum2.sf.net ), since that uses PostGIS.
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.
It’s a little easier to install, but I tend to think defaulting to
SQLite was a mistake.
On Sep 3, 12:04ï¿½am, Marnen Laibow-Koser <rails-mailing-l…@andreas-