Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-3841 LevelDB storage engine
  3. MDEV-4036

LevelDB: INSERT .. ON DUPLICATE KEY UPDATE does not work, produces ER_DUP_KEY

    Details

    • Type: Technical task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Test case:

      create table t1 (pk int primary key, i int) engine=LevelDB;
      insert into t1 values (1,1);
      insert into t1 values (1,100) on duplicate key update i = 100;
      

      The 2nd insert fails with 1022: Can't write; duplicate key in table 't1'

      revision-id: psergey@askmonty.org-20130114131529-qv3531bw9fdklwob
      revno: 4483
      branch-nick: mysql-5.6-leveldb
      

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            psergey Sergei Petrunia added a comment -

            Analyzed. It turns out, Storage Engine API has several calls/members dedicated to ON DUPLICATE KEY UPDATE handling. ha_leveldb doesn't implement them, and this is the reason for error. I'll need to implement them.

            Show
            psergey Sergei Petrunia added a comment - Analyzed. It turns out, Storage Engine API has several calls/members dedicated to ON DUPLICATE KEY UPDATE handling. ha_leveldb doesn't implement them, and this is the reason for error. I'll need to implement them.

              People

              • Assignee:
                psergey Sergei Petrunia
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h