-
Notifications
You must be signed in to change notification settings - Fork 548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve exception naming #260
Comments
I definitely plan on adding specific exceptions for all of the different error types MySQL can return. Just need to find the time to do it (out of town currently). I was planning on going through the list of error codes we can get back from MySQL (via http://dev.mysql.com/doc/refman/5.5/en/error-messages-server.html ?) and create exception classes which extend from Then I can centralize the error handling in Mysql2 itself so that these new exception classes would be raised for those specific error codes. It shouldn't break anyone currently rescuing from |
Just FYI - I'm still planning on doing this but it won't be in 0.3.12 which I'm hoping to release within a couple of days. |
duplicate of #404 |
I think #911 makes good progress. Closing as done! |
All the errors raise the same exception "Mysql2::Error", it would be nice if we have specific exceptions for each error like: "invalid query", "connection closed" etc
so it could be handled on the code
The text was updated successfully, but these errors were encountered: