Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
11.4.3, 10.4(EOL), 10.5, 10.6, 10.11, 11.4
-
None
Description
I run the following test case, in which the INSERT statement should populate the value. However, it failed and returns an error, indicating the dropped column seems to still exist.
CREATE TABLE t0 (c1 INT, c2 BLOB) ROW_FORMAT=REDUNDANT; |
ALTER TABLE t0 DROP c2; |
INSERT INTO t0 (c1) VALUES (0); -- [42000][1118] (conn=10) Row size too large (> 8123). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline. |
Attachments
Issue Links
- is caused by
-
MDEV-15562 Instant DROP COLUMN or changing the order of columns
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue is caused by |
| Component/s | Storage Engine - InnoDB [ 10129 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Fix Version/s | 10.6 [ 24028 ] | |
| Fix Version/s | 10.11 [ 27614 ] | |
| Fix Version/s | 11.4 [ 29301 ] | |
| Affects Version/s | 10.5 [ 23123 ] | |
| Affects Version/s | 10.6 [ 24028 ] | |
| Affects Version/s | 10.11 [ 27614 ] | |
| Affects Version/s | 11.4 [ 29301 ] | |
| Affects Version/s | 10.4(EOL) [ 22408 ] | |
| Assignee | Thirunarayanan Balathandayuthapani [ thiru ] |
| Status | Open [ 1 ] | Confirmed [ 10101 ] |
| Summary | A BLOB column is not properly dropped | Incorrect NULL value handling for instantly dropped BLOB columns |
| Fix Version/s | 10.5.27 [ 29902 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Fix Version/s | 10.6 [ 24028 ] | |
| Fix Version/s | 10.11 [ 27614 ] | |
| Fix Version/s | 11.4 [ 29301 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Confirmed [ 10101 ] | Closed [ 6 ] |
| Fix Version/s | 10.6.20 [ 29903 ] | |
| Fix Version/s | 10.11.10 [ 29904 ] | |
| Fix Version/s | 11.2.6 [ 29906 ] | |
| Fix Version/s | 11.4.4 [ 29907 ] |