Bug #80329 mysqlslap --auto-generate-sql-guid-primary uses incorrect table
Submitted: 10 Feb 2016 14:39 Modified: 11 Feb 2016 12:38
Reporter: Sherzod ODINAEV Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.6.28, 5.6.29 OS:CentOS
Assigned to: CPU Architecture:Any

[10 Feb 2016 14:39] Sherzod ODINAEV
Description:
When using --auto-generate-sql-guid-primary option, the program is supposed to create a column with varchar(36), it creates with varchar(32) instead, and with sql_mode=STRICT_TRANS_TABLES, it throws error

mysqlslap: Cannot run query INSERT INTO t1 VALUES (uuid(),uuid(),uuid(),1804289383,'mxvtvmC9127qJNm06sGB8R92q2j7vTiiITRDGXM9ZLzkdekbWtmXKwZ2qG1llkRw5m9DHOFilEREk3q7oce8O3BEJC0woJsm6uzFAEynLH2xCsw1KQ1lT4zg9rdxBL') ERROR : Data too long for column 'id' at row 1

How to repeat:
Create an option file, I used ~/.my.cnf, stick below in there

[mysqlslap]
auto-generate-sql
auto-generate-sql-execute-number = 10
auto-generate-sql-guid-primary
auto-generate-sql-load-type = 10
auto-generate-sql-secondary-indexes = 2
auto-generate-sql-unique-query-number = 10
auto-generate-sql-unique-write-number = 10
commit = 5
concurrency = 10
iterations = 10
engine = innodb
debug-check
debug-info
EOL

Then SET GLOBAL  sql_mode=STRICT_TRANS_TABLES (or in /etc/my.cnf). When you run the mysqlslap, it will throw an error similar to above.
[11 Feb 2016 12:38] Umesh Shastry
Hello Sherzod,

Thank you for the report.
Verified as described with 5.6.29 build.

Thanks,
Umesh
[3 Mar 2016 1:11] tsubasa tanaka
Is this a same issue of Bug #55265 ?
https://bugs.mysql.com/bug.php?id=55265

I seem Bug#55265 had been fixed only 5.7 series.