[MDEV-15789] mysqlslap --auto-generate-sql-guid-primary and --auto-generate-sql-secondary-indexes use incorrect table definition Created: 2018-04-05 Updated: 2020-08-25 Resolved: 2018-06-07 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Scripts & Clients |
| Affects Version/s: | 10.2.14 |
| Fix Version/s: | 5.5.61, 10.0.36, 10.1.34, 10.2.16, 10.3.8, 10.4.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Calender (Inactive) | Assignee: | Sergey Vojtovich |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | patch | ||
| Description |
|
Note this is an upstream bug in mysqlslap: https://bugs.mysql.com/bug.php?id=80329 But, the bug arises when one uses --auto-generate-sql-guid-primary (and --auto-generate-sql-secondary-indexes) with mysqlslap and also have sql_mode=STRICT_TRANS_TABLE. When using this option, mysqlslap should create a column with varchar(36), but it appears to create it as a varchar(32) only. Then if one has sql_mode=STRICT_TRANS_TABLES, it throws an error, like:
Table structure of t1 in 'mysqlslap' schema:
|
| Comments |
| Comment by Chris Calender (Inactive) [ 2018-04-17 ] | |||||
|
Submitted patch here: | |||||
| Comment by Chris Calender (Inactive) [ 2018-04-17 ] | |||||
|
| |||||
| Comment by Chris Calender (Inactive) [ 2018-06-05 ] | |||||
|
I've completed a majority of the remaining steps (all that I can, and have updated the following accordingly: https://github.com/MariaDB/server/pull/708 Please advise if I need to do anything further. | |||||
| Comment by Sergey Vojtovich [ 2018-06-07 ] | |||||
|
Fix pushed to 5.5, rev. d9b159a2027c56c5c87385cfe1ae43b8c73a97b6 |