Ruby on Rails Friday, July 2, 2010

On Jul 2, 2010, at 12:14 PM, DK wrote:

Hi -
Here are some ideas - at least will be a start at isolating the problem. I am on a Mac so things might not be exact.

1) Here is an example of working database.yml which is working with mysql. You may want to track down the differences and if they are meaningful.

Also, if you have not done, create a test rails app in cmd prompt using: rails testapp -d mysql. This should autogenerate a (potentially) correct database.yml

development:
  adapter: mysql
  encoding: utf8
  reconnect: false
  database: xxx_development
  pool: 5
  username: root
  password:
  socket: /tmp/mysql.sock

2) See if you can log in and access mysql. On a mac I do something in the terminal like: mysql -u [user name] -p [password]. Check out this article http://dev.mysql.com/doc/refman/5.0/en/windows-start-command-line.html. Once you get in see if you can create a db.

On 2 July 2010 12:02, Dave Digital <lists@ruby-forum.com> wrote:
I'm running on Vista 32bit (VMware Fusion).

I installed MySQL with WAMP.

Yes the mysql service is running.


database.yml
------------------------------------------------------------------------

development:
 adapter: mysql
 database: music_library_development
 pool: 5
 timeout: 5000
 host: localhost
In case the "hints" are too subtle, I suspect you took the example and fixed sqlite3 => mysql and set your database name.  Since SQLite doesn't need username/password, you didn't have those in the example.  Put them in and you're probably going to be all set.

-Rob


test:
 adapter: mysql
 database: music_library_test
 pool: 5
 timeout: 5000
 host: localhost

production:
 adapter: mysql
 database: music_library_production
 pool: 5
 timeout: 5000
 host: localhost

No comments:

Post a Comment