-
Notifications
You must be signed in to change notification settings - Fork 22
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
Requires SUPER permissions #12
Comments
This can be worked around by setting the option |
@nlf Would you accept a patch that changes how cleanup works so that it just does the scheduling in node? It shouldn't create a performance issue since the time spent in node will just be initiating the query, and all the work will happen outside of the event loop anyway. If you'd accept that, I'll file an issue for it and start working on a patch. |
Sure, that's a reasonable workaround. I would suggest keeping cleanup optional, however. And the user should be able to decide between having the job in mysql or having it run in node. |
If you want to keep the current implementation as an option, I'd suggest having it try to use the mysql job, and if that fails, check the error code. If it failed because of |
Seems reasonable to me. |
Apparently this requires SUPER permission on the mysql host as line 22 of connect-mysql.js has
connection.query('SET GLOBAL event_scheduler = 1');
which doesn't work for a non-SUPER user.The text was updated successfully, but these errors were encountered: