4493d40a-92aa-4162-9dfc-bfc4ec0996e6
/
polardbxengine
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
polardbxengine/mysql-test/t/key.test

648 lines
22 KiB
Plaintext
Raw Permalink Blame History

# one subtest needs page size > 8k
SET SQL_WARNINGS=1;
#
# This failed for Elizabeth Mattijsen
#
CREATE TABLE t1 (
ID CHAR(32) NOT NULL,
name CHAR(32) NOT NULL,
value CHAR(255),
INDEX indexIDname (ID(8),name(8))
) ;
INSERT INTO t1 VALUES
('keyword','indexdir','/export/home/local/www/database/indexes/keyword');
INSERT INTO t1 VALUES ('keyword','urlprefix','text/ /text');
INSERT INTO t1 VALUES ('keyword','urlmap','/text/ /');
INSERT INTO t1 VALUES ('keyword','attr','personal employee company');
INSERT INTO t1 VALUES
('emailgids','indexdir','/export/home/local/www/database/indexes/emailgids');
INSERT INTO t1 VALUES ('emailgids','urlprefix','text/ /text');
INSERT INTO t1 VALUES ('emailgids','urlmap','/text/ /');
INSERT INTO t1 VALUES ('emailgids','attr','personal employee company');
SELECT value FROM t1 WHERE ID='emailgids' AND name='attr';
drop table t1;
#
# Problem with many key parts and many or
#
CREATE TABLE t1 (
price int(5) DEFAULT '0' NOT NULL,
area varchar(40) DEFAULT '' NOT NULL,
type varchar(40) DEFAULT '' NOT NULL,
transityes enum('Y','N') DEFAULT 'Y' NOT NULL,
shopsyes enum('Y','N') DEFAULT 'Y' NOT NULL,
schoolsyes enum('Y','N') DEFAULT 'Y' NOT NULL,
petsyes enum('Y','N') DEFAULT 'Y' NOT NULL,
KEY price (price,area,type,transityes,shopsyes,schoolsyes,petsyes)
);
INSERT INTO t1 VALUES (900,'Vancouver','Shared/Roomate','N','N','N','N');
INSERT INTO t1 VALUES (900,'Vancouver','Shared/Roomate','N','N','N','N');
INSERT IGNORE INTO t1 VALUES (900,'Vancouver','Shared/Roomate','','','','');
INSERT INTO t1 VALUES (900,'Vancouver','Shared/Roomate','Y','Y','Y','Y');
INSERT INTO t1 VALUES (900,'Vancouver','Shared/Roomate','Y','Y','Y','Y');
INSERT INTO t1 VALUES (900,'Vancouver','Shared/Roomate','Y','Y','Y','Y');
INSERT INTO t1 VALUES (900,'Vancouver','Shared/Roomate','Y','Y','Y','Y');
INSERT INTO t1 VALUES (900,'Vancouver','Shared/Roomate','Y','Y','Y','Y');
SELECT * FROM t1 WHERE area='Vancouver' and transityes='y' and schoolsyes='y' and ( ((type='1 Bedroom' or type='Studio/Bach') and (price<=500)) or ((type='2 Bedroom') and (price<=550)) or ((type='Shared/Roomate') and (price<=300)) or ((type='Room and Board') and (price<=500)) ) and price <= 400;
drop table t1;
#
# No longer a problem with primary key
#
CREATE TABLE t1 (program enum('signup','unique','sliding') not null, type enum('basic','sliding','signup'), sites set('mt'), PRIMARY KEY (program));
# This no longer give an error for wrong primary key
ALTER TABLE t1 modify program enum('signup','unique','sliding');
drop table t1;
#
# Test of compressed decimal index.
#
CREATE TABLE t1 (
name varchar(50) DEFAULT '' NOT NULL,
author varchar(50) DEFAULT '' NOT NULL,
category decimal(10,0) DEFAULT '0' NOT NULL,
email varchar(50),
password varchar(50),
proxy varchar(50),
bitmap varchar(20),
msg varchar(255),
urlscol varchar(127),
urlhttp varchar(127),
timeout decimal(10,0),
nbcnx decimal(10,0),
creation decimal(10,0),
livinguntil decimal(10,0),
lang decimal(10,0),
type decimal(10,0),
subcat decimal(10,0),
subtype decimal(10,0),
reg char(1),
scs varchar(255),
capacity decimal(10,0),
userISP varchar(50),
CCident varchar(50) DEFAULT '' NOT NULL,
PRIMARY KEY (name,author,category)
);
INSERT INTO t1 VALUES
('patnom','patauteur',0,'p.favre@cryo-networks.fr',NULL,NULL,'#p2sndnq6ae5g1u6t','essai salut','scol://195.242.78.119:patauteur.patnom',NULL,NULL,NULL,950036174,-882087474,NULL,3,0,3,'1','Pub/patnom/futur_divers.scs',NULL,'pat','CC1');
INSERT INTO t1 VALUES
('LeNomDeMonSite','Marc',0,'m.barilley@cryo-networks.fr',NULL,NULL,NULL,NULL,'scol://195.242.78.119:Marc.LeNomDeMonSite',NULL,NULL,NULL,950560434,-881563214,NULL,3,0,3,'1','Pub/LeNomDeMonSite/domus_hibere.scs',NULL,'Marq','CC1');
select * from t1 where name='patnom' and author='patauteur' and category=0;
drop table t1;
#
# Problem with search on partial index
#
create table t1
(
name_id int not null auto_increment,
name blob,
INDEX name_idx (name(5)),
primary key (name_id)
);
INSERT t1 VALUES(NULL,'/');
INSERT t1 VALUES(NULL,'[T,U]_axpby');
SELECT * FROM t1 WHERE name='[T,U]_axpy';
SELECT * FROM t1 WHERE name='[T,U]_axpby';
create table t2
(
name_id int not null auto_increment,
name char(255) binary,
INDEX name_idx (name(5)),
primary key (name_id)
);
INSERT t2 select * from t1;
SELECT * FROM t2 WHERE name='[T,U]_axpy';
SELECT * FROM t2 WHERE name='[T,U]_axpby';
# Test possible problems with warnings in CREATE ... SELECT
CREATE TABLE t3 SELECT * FROM t2 WHERE name='[T,U]_axpby';
SELECT * FROM t2 WHERE name='[T,U]_axpby';
drop table t1,t2,t3;
#
# Test bug with long primary key
#
create table t1
(
SEQNO numeric(12 ) not null,
MOTYPEID numeric(12 ) not null,
MOINSTANCEID numeric(12 ) not null,
ATTRID numeric(12 ) not null,
VALUE varchar(120) not null,
primary key (SEQNO, MOTYPEID, MOINSTANCEID, ATTRID, VALUE )
);
INSERT INTO t1 VALUES (1, 1, 1, 1, 'a');
INSERT INTO t1 VALUES (1, 1, 1, 1, 'b');
--error ER_DUP_ENTRY
INSERT INTO t1 VALUES (1, 1, 1, 1, 'a');
drop table t1;
#
# Test of create key order
#
create table t1 (a int not null unique, b int unique, c int, d int not null primary key, key(c), e int not null unique);
analyze table t1;
show keys from t1;
drop table t1;
#
# longer keys
#
create table t1 (i int, a char(200), b text, unique (a), unique (b(300))) charset utf8 row_format=dynamic engine=innodb;
insert ignore t1 values (1, repeat('a',210), repeat('b', 310));
insert ignore t1 values (2, repeat(0xD0B1,215), repeat(0xD0B1, 310));
select i, length(a), length(b), char_length(a), char_length(b) from t1;
select i from t1 where a=repeat(_utf8 'a',200);
select i from t1 where a=repeat(_utf8 0xD0B1,200);
select i from t1 where b=repeat(_utf8 'b',310);
drop table t1;
#
# Test of problem with key read (Bug #3666)
#
CREATE TABLE t1 (numeropost mediumint(8) unsigned NOT NULL default '0', numreponse int(10) unsigned NOT NULL auto_increment, PRIMARY KEY (numeropost,numreponse), UNIQUE KEY numreponse (numreponse));
INSERT INTO t1 (numeropost,numreponse) VALUES ('1','1'),('1','2'),('2','3'),('2','4');
SELECT numeropost FROM t1 WHERE numreponse='1';
EXPLAIN SELECT numeropost FROM t1 WHERE numreponse='1';
FLUSH TABLES;
SELECT numeropost FROM t1 WHERE numreponse='1';
drop table t1;
#
# Bug 6166: index prefix length of 0 not rejected
#
# this test should fail in 5.0
# to fix it, remove #ifdef in
# file sql_yacc.yy(key_part)
# create dedicated error code for this and
# and change my_printf_error() to my_error
--error 1391
create table t1 (c char(10), index (c(0)));
#
# Bug #6126: Duplicate columns in keys should fail
# Bug #6252: (dup)
#
--error 1060
create table t1 (c char(10), index (c,c));
--error 1060
create table t1 (c1 char(10), c2 char(10), index (c1,c2,c1));
--error 1060
create table t1 (c1 char(10), c2 char(10), index (c1,c1,c2));
--error 1060
create table t1 (c1 char(10), c2 char(10), index (c2,c1,c1));
create table t1 (c1 char(10), c2 char(10));
--error 1060
alter table t1 add key (c1,c1);
--error 1060
alter table t1 add key (c2,c1,c1);
--error 1060
alter table t1 add key (c1,c2,c1);
--error 1060
alter table t1 add key (c1,c1,c2);
drop table t1;
#
# Bug#11228: DESC shows arbitrary column as "PRI"
#
create table t1 (
i1 INT NOT NULL,
i2 INT NOT NULL,
UNIQUE i1idx (i1),
UNIQUE i2idx (i2)) charset utf8mb4;
desc t1;
show create table t1;
drop table t1;
#
# If we use a partial field for a key that is actually the length of the
# field, and we extend the field, we end up with a key that includes the
# whole new length of the field.
#
create table t1 (a varchar(10), b varchar(10), key(a(10),b(10))) charset utf8mb4;
show create table t1;
alter table t1 modify b varchar(20);
show create table t1;
alter table t1 modify a varchar(20);
show create table t1;
drop table t1;
#
# Bug #11227: Incorrectly reporting 'MUL' vs. 'UNI' on varchar
#
create table t1 (a int not null primary key, b varchar(20) not null unique);
desc t1;
drop table t1;
create table t1 (a int not null primary key, b int not null unique);
desc t1;
drop table t1;
create table t1 (a int not null primary key, b varchar(20) not null, unique (b(10)));
desc t1;
drop table t1;
create table t1 (a int not null primary key, b varchar(20) not null, c varchar(20) not null, unique(b(10),c(10)));
desc t1;
drop table t1;
# End of 4.1 tests
#
# WL#1563 - Modify MySQL to support on-line CREATE/DROP INDEX
# To test if this really works, you need to run with --debug
# and check the trace file.
#
# Create a table with named and unnamed indexes.
create table t1 (
c1 int,
c2 char(12),
c3 varchar(123),
c4 timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
index (c1),
index i1 (c1),
index i2 (c2),
index i3 (c3),
unique i4 (c4),
index i5 (c1, c2, c3, c4),
primary key (c2, c3),
index (c2, c4)) charset utf8mb4;
show create table t1;
# Some simple tests.
alter table t1 drop index c1;
alter table t1 add index (c1);
# This creates index 'c1_2'.
alter table t1 add index (c1);
alter table t1 drop index i3;
alter table t1 add index i3 (c3);
# Two indexes at the same time.
alter table t1 drop index i2, drop index i4;
alter table t1 add index i2 (c2), add index i4 (c4);
# Three indexes, one of them reversely.
alter table t1 drop index i2, drop index i4, add index i6 (c2, c4);
alter table t1 add index i2 (c2), add index i4 (c4), drop index i6;
# include an unique index.
alter table t1 drop index i2, drop index i4, add unique i4 (c4);
alter table t1 add index i2 (c2), drop index i4, add index i4 (c4);
# Modify an index by changing its definition.
alter table t1 drop index c2, add index (c2(4),c3(7));
# Change nothing. The new key definition is the same as the old one.
alter table t1 drop index c2, add index (c2(4),c3(7));
# Test primary key handling.
alter table t1 add primary key (c1, c2), drop primary key;
alter table t1 drop primary key;
# Drop is checked first. Primary key must exist.
--error 1091
alter table t1 add primary key (c1, c2), drop primary key;
show create table t1;
# Insert non-unique values.
insert into t1 values(1, 'a', 'a', NOW()), (1, 'b', 'b', NOW());
# Drop some indexes for new adds.
alter table t1 drop index i3, drop index i2, drop index i1;
# Add indexes, one is unique on non-unique values.
--error ER_DUP_ENTRY
alter table t1 add index i3 (c3), add index i2 (c2), add unique index i1 (c1);
drop table t1;
#
# Bug #24778: Innodb: No result when using ORDER BY
#
CREATE TABLE t1 (
a INTEGER auto_increment PRIMARY KEY,
b INTEGER NOT NULL,
c INTEGER NOT NULL,
d CHAR(64)
);
CREATE TABLE t2 (
a INTEGER auto_increment PRIMARY KEY,
b INTEGER NOT NULL,
c SMALLINT NOT NULL,
d DATETIME NOT NULL,
e SMALLINT NOT NULL,
f INTEGER NOT NULL,
g INTEGER NOT NULL,
h SMALLINT NOT NULL,
i INTEGER NOT NULL,
j INTEGER NOT NULL,
UNIQUE INDEX (b),
INDEX (b, d, e, f, g, h, i, j, c),
INDEX (c)
);
INSERT INTO t2 VALUES
(NULL, 1, 254, '1000-01-01 00:00:00', 257, 0, 0, 0, 0, 0),
(NULL, 2, 1, '2004-11-30 12:00:00', 1, 0, 0, 0, 0, 0),
(NULL, 3, 1, '2004-11-30 12:00:00', 1, 0, 0, 2, -21600, 0),
(NULL, 4, 1, '2004-11-30 12:00:00', 1, 0, 0, 2, -10800, 0),
(NULL, 5, 1, '2004-11-30 12:00:00', 1, 0, 0, 5, -10800, 0),
(NULL, 6, 1, '2004-11-30 12:00:00', 102, 0, 0, 0, 0, 0),
(NULL, 7, 1, '2004-11-30 12:00:00', 105, 2, 0, 0, 0, 0),
(NULL, 8, 1, '2004-11-30 12:00:00', 105, 10, 0, 0, 0, 0);
INSERT INTO t1 (b, c, d) VALUES
(3388000, -553000, NULL),
(3388000, -553000, NULL);
# psergey/sergefp: This crashes for a mysterious reason with MRR + Semijoin
# opts. TODO: fix it.
#SELECT *
#FROM t2 c JOIN t1 pa ON c.b = pa.a
#WHERE c.c = 1
#ORDER BY c.b, c.d
#;
DROP TABLE t1, t2;
#
# Bug #31137: Assertion failed: primary_key_no == -1 || primary_key_no == 0
#
create table t1(a int not null, key aa(a),
b char(10) not null, unique key bb(b(1)),
c char(4) not null, unique key cc(c)) charset utf8mb4;
desc t1;
show create table t1;
drop table t1;
create table t1(a int not null, key aa(a),
b char(10) not null, unique key bb(b(1)),
c char(4) not null) charset utf8mb4;
desc t1;
alter table t1 add unique key cc(c);
desc t1;
show create table t1;
drop table t1;
--echo End of 5.0 tests
#
# Bug #31148: bool close_thread_table(THD*, TABLE**): Assertion
# 'table->key_read == 0' failed.
#
--disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings
CREATE TABLE t1 (a INT PRIMARY KEY AUTO_INCREMENT);
INSERT INTO t1 VALUES (), (), ();
SELECT 1 AS c1
FROM t1
ORDER BY (
SELECT 1 AS c2
FROM t1
GROUP BY GREATEST(LAST_INSERT_ID(), t1.a)
ORDER BY GREATEST(LAST_INSERT_ID(), t1.a)
LIMIT 1);
DROP TABLE t1;
--echo #
--echo # Additional coverage for handling of key algorithm in index definition.
--echo #
--echo #
--echo # 1) Default case. If key algorithm was not specified explicitly and
--echo # this is normal key (not spatial or fulltext) storage engine
--echo # default key algorithm is used.
--echo #
create table ti (k int, index (k)) charset utf8mb4 engine=innodb;
create table th (k int, index (k)) charset utf8mb4 engine=heap;
--echo #
--echo # Key algorithm is not shown in SHOW CREATE TABLE output in this case
--echo #
show create table ti;
show create table th;
--echo #
--echo # But visible in I_S.STATISTICS
--echo #
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' order by table_name;
--echo #
--echo # Same applies when keys are added by ALTER TABLE
--echo #
alter table ti add column l int, add index (l);
alter table th add column l int, add index (l);
show create table ti;
show create table th;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'l'
order by table_name;
drop tables ti, th;
--echo #
--echo # 2) For SPATIAL and FULLTEXT keys we always use special key
--echo # algorithms and there is no way to specify it explicitly.
--echo #
create table ti (pk int primary key, p point not null SRID 0, spatial index (p))
charset utf8mb4 engine=innodb;
--error ER_CHECK_NOT_IMPLEMENTED
create table th (pk int primary key, p point not null, spatial index (p))
charset utf8mb4 engine=heap;
--echo #
--echo # Key algorithm is not shown in SHOW CREATE TABLE output in this
--echo # case as well.
--echo #
show create table ti;
--echo #
--echo # But visible in I_S.STATISTICS
--echo #
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'p'
order by table_name;
--echo #
--echo # Same applies when keys are added by ALTER TABLE
--echo #
alter table ti add column q point not null SRID 0, add spatial index (q);
show create table ti;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'q'
order by table_name;
drop tables ti;
--echo #
--echo # Same applies to FULLTEXT indexes.
--echo #
create table ti (pk int primary key, v varchar(255), fulltext index (v))
charset utf8mb4 engine=innodb;
--error ER_TABLE_CANT_HANDLE_FT
create table th (pk int primary key, v varchar(255), fulltext index (v))
charset utf8mb4 engine=heap;
show create table ti;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'v'
order by table_name;
--echo #
--echo # Same applies when keys are added by ALTER TABLE
--echo #
alter table ti add column w varchar(255), add fulltext index (w);
show create table ti;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'w'
order by table_name;
drop tables ti;
--echo #
--echo # 3) If key algorithm was specified explicitly and it is supported
--echo # by the storage engine it will be used.
--echo #
create table ti (k int, index using btree (k)) charset utf8mb4 engine=innodb;
create table th (k int, index using btree (k)) charset utf8mb4 engine=heap;
--echo #
--echo # In this case it is shown in SHOW CREATE TABLE output
--echo #
show create table ti;
show create table th;
--echo #
--echo # Also visible in I_S.STATISTICS
--echo #
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' order by table_name;
--echo #
--echo # Same applies when keys are added by ALTER TABLE
--echo #
--echo # Note that the information that algorithm was provided explicitly is
--echo # preserved by ALTER TABLE.
alter table ti add column l int, add index using btree (l);
alter table th add column l int, add index using hash (l);
show create table ti;
show create table th;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'l'
order by table_name;
drop tables ti, th;
--echo #
--echo # 4) If key algorithm was specified explicitly and but it is not
--echo # supported by the storage engine the default algorithm for SE
--echo # will be used instead. We will emit a note in this case. We will
--echo # also treat such situation as if algorithm is implicit.
--echo #
--echo # The below statements should emit notes.
create table ti (k int, index using hash (k)) charset utf8mb4 engine=innodb;
--echo #
--echo # In this case algorithm is not in SHOW CREATE TABLE output
--echo #
show create table ti;
--echo #
--echo # But visible in I_S.STATISTICS
--echo #
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' order by table_name;
--echo #
--echo # Same applies when keys are added by ALTER TABLE
--echo #
alter table ti add column l int, add index using hash (l);
show create table ti;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'l'
order by table_name;
drop tables ti;
--echo #
--echo # 5) Coverage for key algorithm handling in cross-engine ALTER TABLE.
--echo #
--echo # If algorithm was not specified explicitly cross-engine ALTER TABLE
--echo # will silently change it to the new SE's default.
create table t1 (k int, index (k)) charset utf8mb4 engine=innodb;
show create table t1;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'k'
order by table_name;
--echo # Change table's SE.
alter table t1 engine= heap;
--echo # Key definition stays the same in SHOW CREATE TABLE output
show create table t1;
--echo # But in I_S.STATISTICS we see that algorithm has changed.
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'k'
order by table_name;
drop table t1;
--echo #
--echo # If algorithm was specified explicitly and is supported by the new
--echo # SE we will keep it.
--echo #
create table t1 (k int, index using btree (k)) charset utf8mb4 engine=innodb;
show create table t1;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'k'
order by table_name;
--echo # Change table's SE.
alter table t1 engine= heap;
--echo # Key definition stays the same in SHOW CREATE TABLE output
show create table t1;
--echo # In I_S.STATISTICS we also see that algorithm is the same
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'k'
order by table_name;
drop table t1;
--echo #
--echo # If algorithm was specified explicitly but is not supported by the
--echo # new SE, we will used new SE's default instead, emit a note, and
--echo # treat new algorithm as implicitly specified after that.
--echo #
create table t1 (k int, index using hash (k)) charset utf8mb4 engine=heap;
show create table t1;
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'k'
order by table_name;
--echo # Change table's SE. Note will be emitted.
alter table t1 engine= innodb;
--echo # New algorithm is not visible SHOW CREATE TABLE output.
show create table t1;
--echo # In I_S.STATISTICS we see that algorithm has changed.
select table_name, index_type from information_schema.statistics
where table_schema = 'test' and table_name like 't%' and index_name = 'k'
order by table_name;
drop table t1;
--echo #
--echo # 6) Key algorithms and duplicate key detection.
--echo #
--echo # When we detect duplicate keys in table definition we take
--echo # key algorithm into account. But we ignore if it was explicit
--echo # or implicit.
create table t1 (k int, index using btree (k), index using hash (k)) engine=heap;
drop table t1;
create table t1 (k int, index (k), index using hash (k)) engine=heap;
drop table t1;
create table t1 (k int, index using btree (k), index (k)) engine=innodb;
drop table t1;
create table t1 (k int, index using btree (k), index using hash (k)) engine=innodb;
drop table t1;
--echo #
--echo # Bug #27546306 MISSING VITAL ERROR INFORMATION IN ERROR MESSAGE WHEN FAILING TO CONVERT CHARSET
--echo #
--echo #
CREATE TABLE `mytable` ( `id` INT(10) UNSIGNED NOT NULL DEFAULT '0', `somefield` VARCHAR(1000) NOT NULL DEFAULT '',
PRIMARY KEY (`id`,`somefield`) )
DEFAULT CHARSET=UTF8MB3;
--error ER_COLUMN_CHANGE_SIZE
ALTER TABLE mytable CONVERT TO CHARACTER SET UTF8MB4;
DROP TABLE mytable;
--echo #
--echo # Bug 25647413 "ASSERTION FAILURE: HA_INNODB.CC:NNN:(TABLE->INDEXES).
--echo # COUNT == DD_TABLE.INDEXES()".
--echo #
create table t1 (b text not null, unique key(b(8)));
drop table t1;
Reference in New Issue View Git Blame Copy Permalink