Add logic to ignore mysql.events #435
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Travis is failing on us :( |
|
Thanks for the pointer all tests are working now and i added additional ones for this setting. |
apenney
pushed a commit
that referenced
this pull request
Feb 3, 2014
Add logic to ignore mysql.events
|
Thanks for this! |
|
cheers On 3 February 2014 20:49, Ashley Penney notifications@github.com wrote:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mysqldump throws a warning unless you explicitly choose what to do with the events table. See here
http://www.linuxbrigade.com/warning-skipping-data-table-mysql-event/
This current script mails after each cron iteration because of this warning. This small patch adds a variable to control wether to skip the mysql.events table or back it up.