This just bit me on some hand-coded SQL, migrating from SQLite to
MySQL and I didn't get the same results from a query. If you're never
touching hand-written SQL or conditions parameters, then you should be
fine with mix-and-match. But to be absolutely certain, then you can't
beat using the same database in all three environments.
Walter
On Nov 26, 2010, at 10:14 PM, daze wrote:
Should the types of databases for development, testing, and production
all be the same?
Is it okay to have, for example, sqlite3 for development and testing,
and mysql2 for production? Is that doable/common/not too hard to
configure?
--
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-
t...@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
.
--
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-t...@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.
