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

upsert to non-versioning column in versioned table should not, but still, created new record.

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4.12
    • 10.4
    • Versioned Tables
    • None
    • 10.4.12-MariaDB-1:10.4.12+maria~bionic
      docker image from docker hub

    Description

      When enable versioning (timestamp) for whole table except one column, using upsert (insert ... on duplicate update) to update the unversioning column, will still create new version records.

      How to reproduce: https://hackmd.io/WNz_xg9pRYiQrL69QkufrQ

      A workaround is to use txrid (transaction id) based versioning, but it doesn't support partitions to separate current and historic data, still. MDEV-15951

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17089 Updating a System Versioned Table always causes a row to be updated, regardless if the data is the same or not

          • Major - Major loss of function.
          • Closed

          Activity

            People

              midenok Aleksey Midenkov
              bluet BlueT - Matthew Lien
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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