diff options
| author | svoj@mysql.com/june.mysql.com <> | 2007-09-13 15:39:16 +0500 |
|---|---|---|
| committer | svoj@mysql.com/june.mysql.com <> | 2007-09-13 15:39:16 +0500 |
| commit | 84a9e656e00c0aca0e3b5a34bd6a758da7d031d9 (patch) | |
| tree | 82d23f01d2218d826e733d6d8a4d62634c9555bd /mysql-test/t/heap_btree.test | |
| parent | 45647d3bd9fc2d99ebc231c27aee399643ed4f75 (diff) | |
| download | mariadb-git-84a9e656e00c0aca0e3b5a34bd6a758da7d031d9.tar.gz | |
BUG#30590 - delete from memory table with composite btree primary key
DELETE query against memory table with btree index may remove
not all matching rows. This happens only when DELETE uses
index read method to find matching rows. E.g. for queries
like DELETE FROM t1 WHERE a=1.
Fixed by reverting fix for BUG9719 and applying proper solution.
Diffstat (limited to 'mysql-test/t/heap_btree.test')
| -rw-r--r-- | mysql-test/t/heap_btree.test | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/mysql-test/t/heap_btree.test b/mysql-test/t/heap_btree.test index f8d6afbad04..849b7e12843 100644 --- a/mysql-test/t/heap_btree.test +++ b/mysql-test/t/heap_btree.test @@ -213,4 +213,13 @@ CREATE TABLE t1 ( INSERT INTO t1 VALUES('1'), ('2'); DROP TABLE t1; +# +# BUG#30590 - delete from memory table with composite btree primary key +# +CREATE TABLE t1 (a INT, KEY USING BTREE(a)) ENGINE=MEMORY; +INSERT INTO t1 VALUES(1),(2),(2); +DELETE FROM t1 WHERE a=2; +SELECT * FROM t1; +DROP TABLE t1; + --echo End of 4.1 tests |