Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5, 5.5(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
-
None
Description
CREATE TABLE t1 (a VARCHAR(3), v VARCHAR(3) AS (CONCAT('x-',a)) VIRTUAL); |
INSERT INTO t1 (a) VALUES ('foo'); |
SELECT * FROM t1; |
10.2 ab271ee7 |
INSERT INTO t1 (a) VALUES ('foo'); |
SELECT * FROM t1; |
a v
|
foo x-f
|
Reproducible on all of 5.5-10.6.
The expected result would be a warning with non-strict SQL mode and an error with the strict mode. MySQL does exactly that:
MySQL 5.7 3701bd36be with sql-mode='' |
INSERT INTO t1 (a) VALUES ('foo'); |
Warnings:
|
Warning 1265 Data truncated for column 'v' at row 1 |
SELECT * FROM t1; |
a v
|
foo x-f
|
MySQL 5.7 3701bd36be with sql-mode='STRICT_ALL_TABLES' |
mysqltest: At line 2: query 'INSERT INTO t1 (a) VALUES ('foo')' failed: 1406: Data too long for column 'v' at row 1 |
Attachments
Issue Links
- relates to
-
MDEV-24583 ASAN use-after-poison in create_tmp_table or assertion failures after failed REPLACE into table with virtual/stored column
- Closed