Client errors in DatabaseBase->query() are thrown as DBQueryError exceptions, even when the error is clearly related to connectivity, and would be better represented by a DBConnectionError exception. This way, we wouldn't give the goofy suggestion to run maintenance/update.php when we hit a 2013 ("Lost connection to MySQL server during query") client error.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Avoid update.php suggestion on DB connection errors | mediawiki/core | master | +28 -6 |
Related Objects
Related Objects
Event Timeline
Comment Actions
Change 229981 had a related patch set uploaded (by Aaron Schulz):
Avoid update.php suggestion on DB connection errors
Comment Actions
Change 229981 merged by jenkins-bot:
Avoid update.php suggestion on DB connection errors
Comment Actions
Actually using DBConnectionError has it's own pitfalls and changes needed, so the above change just fixes the error message string, which should be fine.