mismatch in results

rowsAffected.sql.ref.log does not match rowsAffected.sql.log.
bug5315.sql.ref.log does not match bug5315.sql.log.

[root@srvss2 srvswdev11]# diff test297/rowsAffected.sql.ref.log test297/rowsAffected.sql.log
31c31
< Query OK, 1 row affected
—
> Query OK, 0 rows affected
46c46
< Query OK, 1 row affected
—
> Query OK, 0 rows affected

In addition to rowsAffected.sql, bug5314sql is also not matching

diff bug5315.sql.ref.log bug5315.sql.log
33c33
< Query OK, 2 rows affected
—
> Query OK, 0 rows affected
56c56
< Query OK, 2 rows affected
—
> Query OK, 0 rows affected
79c79
< Query OK, 2 rows affected
—
> Query OK, 0 rows affected

hill Both of the queries' results are matching with reference log because UPDATE query is reporting incorrect number of rows affected. I tested other UPDATE queries and observed the same.

David.Hall This test suite failed because UPDATE statements is not reporting the number of rows affected correctly - even though values in the table are correctly updated. See the example test I did for UPDATE statement

create table t2(a int, b int)engine=infinidb;

Query OK, 0 rows affected (0.20 sec)

MariaDB [test]> insert into t2 values (1, 2)

    -> ;

Query OK, 1 row affected (0.07 sec)

MariaDB [test]> insert into t2 values (3, 4);

Query OK, 1 row affected (0.04 sec)

MariaDB [test]> select * from t2;

+------+------+                                    

| a    | b    |

+------+------+

|    1 |    2 |

|    3 |    4 |

+------+------+

2 rows in set (0.03 sec)

MariaDB [test]> update t2 set a = 10;

{color:red}Query OK, 0 rows affected (0.06 sec)

Rows matched: 0  Changed: 0  Warnings: 0{color}

MariaDB [test]> select * from t2;

+------+------+                                    

| a    | b    |

+------+------+

|   10 |    2 |

|   10 |    4 |

+------+------+

2 rows in set (0.01 sec)

As you notice above from the result of the select after the UPDATE, the UPDATE statement does update the column a to 10 as expected, but - it still says "0 rows affected"

This is what is causing the test script to report failure -even though in reality update did work. So this is bug in reporting the number of rows affected by UPDATE statement

Running test297.sh.
297 Miscellaneous Tests: Failed (See test297.details)
[root@srvregtest alltest]# cat test297.details
test297 Failure Details:

rowsAffected.sql.ref.log does not match rowsAffected.sql.log.
bug5315.sql.ref.log does not match bug5315.sql.log.
[root@srvregtest alltest]#
[root@srvregtest alltest]#
[root@srvregtest alltest]# cd test297
[root@srvregtest test297]# diff rowsAffected.sql.ref.log rowsAffected.sql.log
46c46
< Query OK, 1 row affected
—
> Query OK, 0 rows affected
[root@srvregtest test297]# diff bug5315.sql.ref.log bug5315.sql.log
79c79
< Query OK, 2 rows affected
—
> Query OK, 0 rows affected

This should now be fixed for UPDATE (see MCOL-72) and DELETE.

297 Miscellaneous Tests: Passed

Woo Hoo

Since in latest regression this test case pass after the fix for UPDATE and DELETE rows - closing this