You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugA problem or regression with an existing featurehas-prAn issue that has a pull request pending that may fix this issue. The pull request may be incomplete
Apparently, when updating an event in phpMyAdmin, it issues a DROP EVENT `event_name` statement before the CREATE EVENT `event_name`.
This can cause problems in replication in Google CloudSQL migrations as they don't migrate SQL-Events to read-replica instances.
Thereby the replication fails beyond repair as it runs into an SQL error.
It would be more appropriate if phpMyAdmin will use DROP EVENT IF EXISTS `event_name`
The text was updated successfully, but these errors were encountered:
williamdes
added
Bug
A problem or regression with an existing feature
has-pr
An issue that has a pull request pending that may fix this issue. The pull request may be incomplete
labels
Jan 13, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
BugA problem or regression with an existing featurehas-prAn issue that has a pull request pending that may fix this issue. The pull request may be incomplete
Apparently, when updating an event in phpMyAdmin, it issues a DROP EVENT `event_name` statement before the CREATE EVENT `event_name`.
This can cause problems in replication in Google CloudSQL migrations as they don't migrate SQL-Events to read-replica instances.
Thereby the replication fails beyond repair as it runs into an SQL error.
It would be more appropriate if phpMyAdmin will use DROP EVENT IF EXISTS `event_name`
The text was updated successfully, but these errors were encountered: