[MDEV-5974] MySQL Bug #11763174: INFORMATION_SCHEMA.PARAMETERS.NUMERIC_PRECISION SHOULD BE BIGINT Created: 2014-03-28  Updated: 2015-06-09  Resolved: 2015-06-09

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.0.9
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Sergey Vojtovich Assignee: Sergei Golubchik
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-4784 merge test cases from 5.6 Stalled

 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.



 Comments   
Comment by Sergei Golubchik [ 2015-06-09 ]

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"

Generated at Thu Feb 08 07:08:26 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.