Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
Description
2022-06-10 22:45:20 8 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: UPDATE t1 SET c1=REPEAT('xyz',85), c2=REPEAT(c1, 100) ORDER by c1 LIMIT 2
|
Please add a "." after "predicted" and before "Statement" ("predicted. Statement\:") to increase legibility for users.
While doing the change also propose to change "since" to "as". Thanks
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
{noformat}
2022-06-10 22:45:20 8 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: UPDATE t1 SET c1=REPEAT('xyz',85), c2=REPEAT(c1, 100) ORDER by c1 LIMIT 2 {noformat} Please add a "." after "predicted" and before "Statement" (predicted. Statement:) to increase legibility for users. While doing the change also propose to change "since" to "as". Thanks |
{noformat}
2022-06-10 22:45:20 8 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: UPDATE t1 SET c1=REPEAT('xyz',85), c2=REPEAT(c1, 100) ORDER by c1 LIMIT 2 {noformat} Please add a "." after "predicted" and before "Statement" (predicted. Statement\:) to increase legibility for users. While doing the change also propose to change "since" to "as". Thanks |
| Description |
{noformat}
2022-06-10 22:45:20 8 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: UPDATE t1 SET c1=REPEAT('xyz',85), c2=REPEAT(c1, 100) ORDER by c1 LIMIT 2 {noformat} Please add a "." after "predicted" and before "Statement" (predicted. Statement\:) to increase legibility for users. While doing the change also propose to change "since" to "as". Thanks |
{noformat}
2022-06-10 22:45:20 8 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted Statement: UPDATE t1 SET c1=REPEAT('xyz',85), c2=REPEAT(c1, 100) ORDER by c1 LIMIT 2 {noformat} Please add a "." after "predicted" and before "Statement" ("predicted. Statement\:") to increase legibility for users. While doing the change also propose to change "since" to "as". Thanks |
| Labels | warning |
| Labels | warning | beginner-friendly warning |
zhibozhang, thanks for the heads up. But it'd make more sense to add up a single-liner to a first bug-fixes commit to 10.3 which we have - e.g MDEV-28530. I'd rather we do that.
| Status | Open [ 1 ] | In Progress [ 3 ] |
Roel, thanks for description suggestions. Still, considering not to change much in GA:s I picked only the punctuation part for them. I'll exchange with bnestere on the wording part that you pointed and then we'll decide
how to handle 10.10 merge.
| Fix Version/s | 10.3.37 [ 28404 ] | |
| Fix Version/s | 10.4.27 [ 28405 ] | |
| Fix Version/s | 10.5.18 [ 28421 ] | |
| Fix Version/s | 10.6.10 [ 28407 ] | |
| Fix Version/s | 10.7.6 [ 28408 ] | |
| Fix Version/s | 10.8.5 [ 28308 ] | |
| Fix Version/s | 10.9.3 [ 28409 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Fix Version/s | 10.4 [ 22408 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Fix Version/s | 10.6 [ 24028 ] | |
| Fix Version/s | 10.7 [ 24805 ] | |
| Fix Version/s | 10.8 [ 26121 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
Hi Andrei, I will take over to deal with this issue if you do not mind!