-
Notifications
You must be signed in to change notification settings - Fork 18
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
override default healthcheck support #35
Conversation
Is there any reason not to just change the current health check query to |
Maybe I over-engineered it a little bit, but I think it could be for future-proofing. Like in case query log enabled for debugging and you don't want it full of |
Even better, would be nice if For now I'm tempted to change it to |
the current what I really concern at that time (sorry I wrote those at 3AM :D) is that give it a little more flexibility, who knows if some future sql-like database in the future support |
Pushed a change that:
|
@outersky curious what you think. I'm hesitant but seems that my PR blackbeam/rust-mysql-simple#355 to change the |
Also for the CI fail: We'll rebase this after #37 is merged. |
superseded by #38 |
I'm currently using this crate to communicate with my manticore server, even though it's compatible wit MySQL but for some reason it's not support
SELECT version()
which make the default healthcheck always throw error.So I'm adding a feature to override the default healthcheck function.