Hi Greg, That's a good thing - means your gem for mysql is fine. I would try a few other things - it really sounds like it's on the server side of mysql..
What version of mysql are you running? I would create the library_development DB from scratch and try to migrate your beginning data using db:migrate. You will find out right away if there is a communication error. It could be that there's an authentication error or a trouble with communication to the server. I've seen this exact error when I tried to use the newest version of mysql and so I had to go back to an older version. If this gives you a lot of issues, you could try going to sqlite3 or postgresql.. -- Posted via http://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 -~----------~----~----~----~------~----~------~--~---
