diff options
author | Vlad Lesin <vlad_lesin@mail.ru> | 2017-11-30 00:41:43 +0300 |
---|---|---|
committer | Daniel Black <daniel@mariadb.org> | 2020-10-24 22:43:21 +1100 |
commit | f679d72679376d04c863e80bc68d084eb56795a5 (patch) | |
tree | 05785e3eea0f388b089b8784a73be4bc302cffa4 /mysql-test/t | |
parent | 06af03677cf5ad26b733d6250305d75412ed9201 (diff) | |
download | mariadb-git-f679d72679376d04c863e80bc68d084eb56795a5.tar.gz |
MDEV-24017: Blackhole : Specified key was too long; max key length is 1000 bytes
The maximum innodb key length is 3500 what is hardcoded in
ha_innobase::max_supported_key_length()). The maximum number of innodb indexes
is configured with MAX_INDEXES macro (see also MAX_KEY definition).
The same is currently implemented for blackhole storage engine.
Cherry picked from percona-server 0d90d81c3c507a6b1476246a405504f6e4ef9d4d
Original lp bug 1733049
Reviewed-by: daniel@mariadb.org
Diffstat (limited to 'mysql-test/t')
-rw-r--r-- | mysql-test/t/blackhole.test | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/mysql-test/t/blackhole.test b/mysql-test/t/blackhole.test index 7f394e0f846..c80ceffef4c 100644 --- a/mysql-test/t/blackhole.test +++ b/mysql-test/t/blackhole.test @@ -38,3 +38,19 @@ SELECT 0 FROM t1 FORCE INDEX FOR GROUP BY(a) WHERE a = 0 OR b = 0 AND c = 0; DROP TABLE t1; --echo End of 5.6 tests + +# +# MDEV-24017 / bug 53588 test case. +# +# Create long enough index (between 1000 and 3500). 1000 is the old value, +# 3500 is innodb value (see ha_innobase::max_supported_key_length()). Without +# the fix the test will fail with "Specified key was too long" error. +# +CREATE TABLE `t` ( + `a` varchar(3000) NOT NULL default '', + PRIMARY KEY (`a`) +) ENGINE=BLACKHOLE; + +DROP TABLE `t`; + +--echo End of 10.1 tests |