views:

1095

answers:

4

I made an app in Ruby on Rails and now I want to get it hosted. However, they require that I use MySQL and I set it up using sqLite3. Is there any way to convert it to use MySQL?

+5  A: 

As long as you have not written any SQL statements that run in sqlLite3 and not MySQL (which you won't have if all your database access is via ActiveRecord and ActiveRecord migrations) then all you need to do is change the database adapter in your database.yml config file.

DanSingerman
and rake the new database ;)
thismat
you mean rake db:migrate?
Austin
Yes, you'll need to run rake db:migrate in the new environment (but that will be true of any new environment whether it is a different database engine or not.)
DanSingerman
+3  A: 

Check Taps. I've successfully converted a Mysql database to Postgres with it --it should support SQLite.

pantulis
I had to do this recently, Taps worked like a charm, check out this blog entry for examples:http://adamblog.heroku.com/past/2009/2/11/taps_for_easy_database_transfers/
Jack Chu
taps is an awesome utility, definitely worth to check it out
knoopx
link broken, http://adam.heroku.com/past/2009/2/11/taps_for_easy_database_transfers/ seems to work
conny
+3  A: 

If there's no data to migrate, simply update database.yml and run 'rake db:schema:load' in the new environment. (NOT db:migrate which should only be used for incremental migrations!)

ScottJ
+9  A: 

Step 0

To be safe, I recommend experimenting a bit with this technique in a virtual machine. Save yourself a bunch of heartache and build a virtual machine, check out your code, and have a safe playground that you can throw away if tragedy strikes.

Step 1

Make a backup copy of your database.yml file.

(from your application root)

cp config/database.yml config.database.yml.sqlite3

Step 2

Make a backup copy of your data

Install YAML DB plugin

script/plugin install git://github.com/adamwiggins/yaml_db.git

Run the dump task

rake db:dump

Step 3

Update your config/database.yml file. You will find entries like

development:
  adapter: sqlite3
  database: db/development.sqlite3
  timeout: 5000
test:
  adapter: sqlite3
  database: db/test.sqlite3
  timeout: 5000
production:
  adapter: sqlite3
  database: db/production.sqlite3
  timeout: 5000

Change them to

development:
  adapter: mysql
  encoding: utf8
  reconnect: false
  database: **myapp_development**
  pool: 5
  username: **root**
  password: **supersecretpassword**
  **socket: /opt/local/var/run/mysql5/mysqld.sock**
test:
  adapter: mysql
  encoding: utf8
  reconnect: false
  database: **myapp_test**
  pool: 5
  username: **root**
  password: **supersecretpassword**
  socket: **/opt/local/var/run/mysql5/mysqld.sock**

production:
  adapter: mysql
  encoding: utf8
  reconnect: false
  database: **myapp_production**
  pool: 5
  username: **root**
  password: **supersecretpassword**
  socket: **/opt/local/var/run/mysql5/mysqld.sock**

Be sure to update the values surrounded by asterix as appropriate for your platform! The socket value is only good for Mac OSX using MacPorts. Most flavors of linux do not require this value.

Step 5

If you have some errors in the following step, you might have to install the mysql gem:

sudo gem install mysql

Have rake create your database

rake db:create
rake db:schema:load

Step 6

Use YamlDb to reload your data into MySql

rake db:load

marshally
You really should use db:schema:load instead of db:migrate for creating new databases.
ScottJ
actually, why do you need to use Virtual Machine? I thought you can commit your whole Rails project folder to Git or Mercurial or SVN, or even copy the whole folder to a different one, and all data including the sqlite DB data is there, able to be used as a Rails app again.
動靜能量