Page MenuHomePhabricator

Distinguish more carefully between different kinds of MySQL connection errors
ClosedPublic

Authored by epriestley on Jan 21 2016, 8:59 PM.
Tags
None
Referenced Files
F13273321: D15078.diff
Fri, May 31, 1:48 AM
F13263208: D15078.id36408.diff
Mon, May 27, 7:55 AM
F13237864: D15078.id36408.diff
Tue, May 21, 3:34 PM
F13232355: D15078.diff
Tue, May 21, 1:13 AM
F13215431: D15078.id36406.diff
Fri, May 17, 5:16 PM
F13211141: D15078.diff
Fri, May 17, 5:31 AM
F13208711: D15078.id36406.diff
Thu, May 16, 6:53 PM
F13196442: D15078.diff
Sun, May 12, 11:16 PM
Subscribers
None

Details

Summary

Ref T10195. Root issue: if the MySQL user doesn't have permission to access all the databases, we give them a fairly generic error instead of telling them exactly what's wrong.

Currently, we throw a generic exception on connection failure. Instead, throw a more granular one, and distinguish between bad credentials and no access.

Test Plan

See next revision.

Diff Detail

Event Timeline

epriestley retitled this revision from to Distinguish more carefully between different kinds of MySQL connection errors.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Jan 21 2016, 8:59 PM
This revision was automatically updated to reflect the committed changes.