| Bug #58042 | Statements test fails due to max_key_length breach | ||
|---|---|---|---|
| Submitted: | 8 Nov 2010 10:20 | Modified: | 8 Nov 2010 10:26 |
| Reporter: | Tonci Grgin | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / J | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | QA | ||
[8 Nov 2010 10:26]
Tonci Grgin
Pushed up to revision 996.
[9 Nov 2010 8:21]
Tonci Grgin
Reflection of Bug#4541.
Description: Statements.Test, setUp() fails to create table statement_batch_test: mysql> CREATE TABLE statement_batch_test -> (id int not null primary key auto_increment, -> strdata1 varchar(255) not null, strdata2 varchar(255), -> UNIQUE INDEX (strdata1)); ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes How to repeat: - Suggested fix: Check for failure and adjust to max_key_length.