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

INET6_NTOA(ucs2_input) erroneously returns NULL

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
    • 10.4.1
    • Data types
    • None

    Description

      SELECT HEX(INET6_ATON('1::1')), HEX(INET6_ATON(CONVERT('1::1' USING ucs2)));


      +----------------------------------+---------------------------------------------+
      		 
      | HEX(INET6_ATON('1::1'))          | HEX(INET6_ATON(CONVERT('1::1' USING ucs2))) |
      		 
      +----------------------------------+---------------------------------------------+
      		 
      | 00010000000000000000000000000001 | NULL                                        |
      		 
      +----------------------------------+---------------------------------------------+

      Looks wrong. The result for the second column should be equal to the first column.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-274 The data type for IPv6/IPv4 addresses in MariaDB

          • Major - Major loss of function.
          • Closed

          Activity

            People

              bar Alexander Barkov
              bar Alexander Barkov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 3h
                  3h

                  Git Integration

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