Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
database system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Sep 2010 at 15:05 UTC
Updated:
16 Mar 2015 at 02:53 UTC
Jump to comment: Most recent
Comments
Comment #1
David_Rothstein commentedI can reproduce this - the error message looks like this:
It seems very unlikely to me that this is a Drupal bug though. (It could be related to http://bugs.php.net/bug.php?id=46457 and issues linked therein although those were marked fixed a while ago.)
Also, when I tested it, this did not actually prevent the connection in the case where the MySQL username did not have an associated password (leaving the password blank in that case still worked fine and allowed the installation to continue). This only occurred for the case where you need to provide a password but don't, so that you would expect some kind of error message either way.
Was that your experience too? If so, this seems like only a minor bug.
Comment #2
catchDamZ noticed that the default implementation of cache_get() just eats exceptions, that was introduced with http://drupal.org/node/325169#comment-2593568 - which is why this points to lock_may_be_available(). Was introduced by this patch:
http://drupal.org/node/325169#comment-2593568
Comment #3
dcam commentedI can't reproduce this old bug, neither when installing a fresh site nor when deleting the password from an existing site, so I'm closing the issue.