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

BIGINT UNSIGNED treated as SIGNED

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.2.38, 10.5.10
    • Fix Version/s: None
    • Component/s: Data types
    • Labels:
      None
    • Environment:
      For 10.2.38: Linux cpanel8.c.fozzy.com 3.10.0-962.3.2.lve1.5.49.el7.x86_64 #1 SMP Thu Mar 4 05:39:46 EST 2021 x86_64 x86_64 x86_64 GNU/Linux
      For 10.5.10: Windows 10.0.19042.985 x64

      Description

      I have encountered a strange behavior/inconsistency with how MariaDB is working with large values of BIGINT UNSIGNED. It appears that if BIGINT UNSIGNED is used and a value is larger than 9223372036854775807 (max value of BIGINT SIGNED) insert of rows with such values can fail under unknown conditions. It plagues transactions mainly, but I did have 1 case outside of a transaction as well.
      Code samples and more details can be checked in https://dba.stackexchange.com/questions/293791/missing-an-inserted-row
      I will be trying to get a consistent way to replicate this and update both StackExchange and this bug report as soon as I find any new info.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              Simbiat Dmitry Kustov
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated: