Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-35122

Incorrect NULL value handling for instantly dropped BLOB columns

Details

    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

          Task - A task that needs to be done. MDEV-15562 Instant DROP COLUMN or changing the order of columns

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              thiru Thirunarayanan Balathandayuthapani
              John Jove John Jove
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.