Bug #20360 | mysqltest: inconsistent case comparison of SQLSTATE error values | ||
---|---|---|---|
Submitted: | 9 Jun 2006 14:19 | Modified: | 7 Nov 2006 18:17 |
Reporter: | Paul DuBois | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Tests | Severity: | S3 (Non-critical) |
Version: | 4.1 and up | OS: | |
Assigned to: | Magnus Blåudd | CPU Architecture: | Any |
[9 Jun 2006 14:19]
Paul DuBois
[11 Jun 2006 8:11]
Valeriy Kravchuk
Thank you for a problem report. Verified just as described with 4.1-BK and 5.0.23-BK: openxs@suse:~/dbs/5.0> bin/mysqltest test --error s42s02 mysqltest: At line 1: Invalid argument in error s42s02 not ok openxs@suse:~/dbs/5.0> bin/mysqltest test --error S42s02 drop table t; mysqltest: At line 2: query 'drop table t' failed with wrong sqlstate 42S02: 'Un known table 't'', instead of 42s02... not ok
[12 Oct 2006 17:52]
Magnus Blåudd
Pushed to 4.1-maint, 5.0-maint and 5.1-maint
[7 Nov 2006 10:58]
Magnus Blåudd
SQLSTATE string - Must be SQLSTATE_LENGTH long - May contain only digits[0-9] and _uppercase_ letters
[7 Nov 2006 18:17]
Paul DuBois
No changelog entry needed, but I have updated the mysqltest manual with the required syntax for SQLSTATE values.