# Problem with database.yml moving from 0.13.0 to 0.14.4

**URL:** <https://www.ruby-forum.com/t/problem-with-database-yml-moving-from-0-13-0-to-0-14-4/58879>\
**Category:** Rails\
**Created:** [April 26, 2006, 9:07pm UTC](https://www.ruby-forum.com/t/problem-with-database-yml-moving-from-0-13-0-to-0-14-4/58879 "2006-04-26T21:07:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sfmcfar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d9b06d/32.png) [@sfmcfar](https://www.ruby-forum.com/u/sfmcfar)\
**Post date:** [April 26, 2006, 9:07pm UTC](https://www.ruby-forum.com/t/problem-with-database-yml-moving-from-0-13-0-to-0-14-4/58879/1 "2006-04-26T21:07:36Z")

</div>

Hi,

I’m upgrading from 0.13.0 to 0.14.4, and I’m having trouble with my  
database  
authentication. Even though the entries in my database.yml are correct,  
I  
get the  
following message when trying to do a ruby script/generate scaffold  
myClass…

Access denied for user: '@localhost to database ‘’

Why is the username and database name showing up as blank? Like I said,  
I’ve checked my  
enteries in database.yml a dozen times and they are absolutely correct.

Thanks in advance,

-stan

–  
View this message in context:  
[http://www.nabble.com/problem-with-database.yml-moving-from-0.13.0-to-0.14.4-t1513579.html#a4107588](http://www.nabble.com/problem-with-database.yml-moving-from-0.13.0-to-0.14.4-t1513579.html#a4107588)  
Sent from the RubyOnRails Users forum at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![sfmcfar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d9b06d/32.png) [@sfmcfar](https://www.ruby-forum.com/u/sfmcfar)\
**Post date:** [April 27, 2006, 1:31am UTC](https://www.ruby-forum.com/t/problem-with-database-yml-moving-from-0-13-0-to-0-14-4/58879/2 "2006-04-27T01:31:36Z")

</div>

Sounds like you’re using MySQL and although I’m not a MySQL user I  
seem to recall a change about then with having to add the port into  
the database.yml even if it’s using the default of 3306 otherwise it  
tries to connect via unix socket.

hth,  
Dan

---

<div class="post-metadata">

**Author:** ![sfmcfar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d9b06d/32.png) [@sfmcfar](https://www.ruby-forum.com/u/sfmcfar)\
**Post date:** [April 27, 2006, 1:40am UTC](https://www.ruby-forum.com/t/problem-with-database-yml-moving-from-0-13-0-to-0-14-4/58879/3 "2006-04-27T01:40:42Z")

</div>

## Thx. I’ll try when I get back to work tomorrow. Do you know if the hash password warning at the top of the database.yml file could have anything to do with it? We’re still running MySQL 4.0.x at work.

View this message in context:  
[http://www.nabble.com/problem-with-database.yml-moving-from-0.13.0-to-0.14.4-t1513579.html#a4111860](http://www.nabble.com/problem-with-database.yml-moving-from-0.13.0-to-0.14.4-t1513579.html#a4111860)  
Sent from the RubyOnRails Users forum at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![sfmcfar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d9b06d/32.png) [@sfmcfar](https://www.ruby-forum.com/u/sfmcfar)\
**Post date:** [April 27, 2006, 1:53am UTC](https://www.ruby-forum.com/t/problem-with-database-yml-moving-from-0-13-0-to-0-14-4/58879/4 "2006-04-27T01:53:07Z")

</div>

No idea sorry mate, that’s the extent of my mysql knowledge right there  
😉