Investigate incorrected affected rows in Admin #4855
Description
It seems that affected rows is not reset in Admin when executing queries that do not return affected rows, like DDL .
Here an example:
mysql> INSERT INTO tbl1 SELECT id+8192*32 FROM tbl1;
Query OK, 262144 rows affected (0.06 sec)
mysql> INSERT INTO tbl1 SELECT id+8192*64 FROM tbl1;
Query OK, 524288 rows affected (0.10 sec)
mysql>
mysql> DROP TABLE tbl2;
Query OK, 524288 rows affected (0.00 sec)
mysql> CREATE TABLE tbl2 (id INT, v1 TEXT, v2 TEXT, v3 TEXT);
Query OK, 524288 rows affected (0.00 sec)
mysql> DO 1;
ERROR 1045 (28000): ProxySQL Admin Error: near "DO": syntax error
mysql> CREATE TABLE tbl3 (id INT, v1 TEXT, v2 TEXT, v3 TEXT);
Query OK, 524288 rows affected (0.00 sec)
mysql> DROP TABLE tbl2;
Query OK, 524288 rows affected (0.00 sec)
mysql> CREATE TABLE stats.tbl2 (id INT, v1 TEXT, v2 TEXT, v3 TEXT);
Query OK, 524288 rows affected (0.01 sec)
We also need to investigate if this affect SQLite3 Server.
VACUUM seems affected too:
mysql> VACUUM stats;
Query OK, 2097152 rows affected (0.86 sec)