-
Notifications
You must be signed in to change notification settings - Fork 441
Error messages with code above 4000 on MariaDB are not displayed #187
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
Comments
It's not business of this project. |
Excellent!!! Thanks for the quick response. |
It is business of this project, certainly. The check else if (merr > CR_MAX_ERROR) { is wrong both for MariaDB and MySQL. There is no client library where CR_MAX_ERROR is the highest possible error number. It is (and always was) highest possible client error number. Server error numbers can be both below and above that. In MariaDB and in MySQL. |
I'm sorry. I received mail about building almost every day and totally tired. |
No problem! Thanks for the quick fix! |
Guys, You made my day. Perfect. After a git fetch and rebase, reinstall, I now get the real message in my tests ;)
Thanks a lot for keeping the quality of mariadb and its python driver at this level. Regards, Antoine |
Hello,
When using a model with too many CTEs, I get the error
Code: 4003 SQL State: HY000 Too many WITH elements in WITH clause
when doing an explain but the python client/driver (MySQLdb) does not display it and it displayed an cryptic error (''error totally whack').
A deeper source code analysis shows that the python code expects an error code to be below CR_MAX_ERROR
but CR_MAX_ERROR is defined by mariadb as ,
Did this number increase without (mariadb | python-driver) being updated ?
Thanks in advance,
Antoine
PS: I already filed a bug with mariadb here : https://jira.mariadb.org/browse/MDEV-12990
The text was updated successfully, but these errors were encountered: