Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
N/A
-
None
Description
The test case is based on an attempt to load a mariadb-dump dump, foreign_key_checks and unique_checks settings come from there. Only transaction isolation level is a custom setting (originally a startup option). Also reproducible with READ UNCOMMITTED.
--source include/have_innodb.inc
|
|
SET unique_checks=0, foreign_key_checks=0; |
SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED; |
|
CREATE TABLE t (v VECTOR(1) NOT NULL, VECTOR (v)) ENGINE=InnoDB; |
INSERT INTO t VALUES (0x31313131),(0x32323232); |
|
# Cleanup
|
DROP TABLE t; |
6945a4af85fb8e1af6b36aadde0485645ac6a77e |
CURRENT_TEST: bug.w4
|
mysqltest: At line 7: query 'INSERT INTO t VALUES (0x31313131),(0x32323232)' failed: ER_KEY_NOT_FOUND (1032): Can't find record in 't'
|
Attachments
Issue Links
- is caused by
-
MDEV-34939 vector search in 11.7
- Closed