MySQL Warning: Statement may not be safe to log in statement form #4156
Assignees
Labels
Bug
For errors / faults / flaws / inconsistencies etc.
Comments
|
In ce6254e: Thanks for the report. Could you apply this patch and confirm it is working for you? Fixes #4156 Adding ORDER BY clause when DELETING so that it works with replication |
|
In e1a7aca: Thanks for the report. Could you apply this patch and confirm it is working for you? Fixes #4156 Adding ORDER BY clause when DELETING so that it works with replication |
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
…orking for you? Fixes matomo-org#4156 Adding ORDER BY clause when DELETING so that it works with replication https://dev.mysql.com/doc/refman/5.1/en/replication-features-limit.html
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
…orking for you? Fixes matomo-org#4156 Adding ORDER BY clause when DELETING so that it works with replication https://dev.mysql.com/doc/refman/5.1/en/replication-features-limit.html (cherry picked from commit ce6254e)
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using replication, MySQL Reports the following error:
The solution is to add ORDER_BY to the statement. See https://dev.mysql.com/doc/refman/5.1/en/replication-features-limit.html
The text was updated successfully, but these errors were encountered: