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

REPLACE doesn't work with unique blobs on MyISAM table

Details

    Description

      CREATE TABLE t (b BLOB, UNIQUE(b)) ENGINE=MyISAM;
      INSERT INTO t VALUES ('foo');
      REPLACE INTO t VALUES ('foo');
       
      # Cleanup
      DROP TABLE t;
      

      bb-10.4-release-long_unique 5ddae0e0

      mysqltest: At line 3: query 'REPLACE INTO t VALUES ('foo')' failed: 1062: Duplicate entry 'foo' for key 'b'
      

      I'm not sure whether it's supposed to work or not.

      InnoDB currently produces an assertion failure similar to MDEV-18731.

      Attachments

        Issue Links

          Activity

            elenst Elena Stepanova created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            serg Sergei Golubchik made changes -
            Assignee Sachin Setiya [ sachin.setiya.007 ] Sergei Golubchik [ serg ]
            serg Sergei Golubchik made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            serg Sergei Golubchik made changes -
            Status In Progress [ 3 ] Stalled [ 10000 ]
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Fix Version/s 10.4.4 [ 23310 ]
            Fix Version/s 10.4 [ 22408 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 92863 ] MariaDB v4 [ 155810 ]
            bar Alexander Barkov made changes -

            People

              serg Sergei Golubchik
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.