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

MySQL Bug #11763174: INFORMATION_SCHEMA.PARAMETERS.NUMERIC_PRECISION SHOULD BE BIGINT

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Minor
        • Resolution: Won't Fix
        • Affects Version/s: 10.0.9
        • Fix Version/s: N/A
        • Component/s: OTHER
        • Labels:
          None

          Description

          Test case for MySQL "Bug #11763174: INFORMATION_SCHEMA.PARAMETERS.NUMERIC_PRECISION SHOULD BE BIGINT" fails in 10.0.

          Relevant revision:

          revno: 2876.368.165
committer: Mayank Prasad <mayank.prasad@oracle.com
branch nick: trunk_IS
timestamp: Sat 2011-03-12 00:23:12 +0530
message:
  Bug #11763174: INFORMATION_SCHEMA.PARAMETERS.NUMERIC_PRECISION SHOULD BE BIGINT

  Issue:
  ------
  The information_schema.PARAMETERS.NUMERIC_PRECISION and information_schema.ROUTINES.NUMERIC_PRECISION were INT whereas they should have been BIGINT(21) UNSIGNED.

  Solution:
  ---------
  Changed the metadata to return the new column types.
  Added a new test case in main.information_schema.test.
  Updated funcs_1.is_columns_is, main.information_schema_parameters and main.information_schema.routines test result to reflect the new type.

            Gliffy Diagrams

              Attachments

                Issue Links

                is part of

                Task - A task that needs to be done. MDEV-4784 merge test cases from 5.6

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Stalled

                  Activity

                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  Why should it be BIGINT? SQL standard (2003) says that it should be in the INFORMATION_SCHEMA.CARDINAL_NUMBER domain, and this domain "contains any non-negative number that is less than or equal to the implementation-defined maximum for INTEGER"

                  Show
                  serg Sergei Golubchik added a comment - Why should it be BIGINT? SQL standard (2003) says that it should be in the INFORMATION_SCHEMA.CARDINAL_NUMBER domain, and this domain "contains any non-negative number that is less than or equal to the implementation-defined maximum for INTEGER"

                    People

                    • Assignee:
                      serg Sergei Golubchik
                      Reporter:
                      svoj Sergey Vojtovich
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      2 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: