| Bug #8455 | mysqltest, wrong number of affected rows (equals number of warnings) | ||
|---|---|---|---|
| Submitted: | 11 Feb 2005 20:13 | Modified: | 15 May 2005 23:18 |
| Reporter: | Matthias Leich | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S2 (Serious) |
| Version: | 4.1.13-pre | OS: | Any (all) |
| Assigned to: | Kent Boortz | CPU Architecture: | Any |
[11 Feb 2005 20:14]
Matthias Leich
test case
Attachment: ml22.test (application/test, text), 1.17 KiB.
[15 May 2005 23:26]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/24925
Description: "mysqltest" seems to be buggy compared to "mysql". If I enable the extended informations via "--enable-info" and execute an UPDATE where 2 warnings occur, two strange things happen: - the usual line info: Rows matched: <n> Changed: <n> Warnings: <n> disappears and - the printed number of affected rows equals correct number of affected rows * warnings per row I assume this bug is not a problem of the server or the C-API, because the tool "mysql" does show the correct number of affected rows. Please have a look into my test case. My environment: - Intel PC with Linux(SuSE 9.1) - MySQL compiled from source ChangeSet@1.1840.1.27, 2005-02-11 How to repeat: Please use my test script ml22.test , copy it to mysql-test/t ./mysql-test-run ml22 and compare the results with the statements and comments within ml22.test .