[DERBY-1745] System catalog columns of type BIGINT and INT created with incorrect precision of zero.

• Type: Task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6
• Component/s: SQL
• Labels: derby_triage10_11
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 22/Aug/06 17:45
• Updated: 25/Jun/13 05:07

Description

Due to the way system column metadata was handled in the code system columns of these types are always created with precision 0.
User defined columns of these types will have precision 10 (INT) and 19 (BIGINT)
DERBY-1734 will fix this for 10.3 and hopefully 10.2 by a merge before the release.
This bug is here to investigate upgrade issues and fix them if required.
Not known of any incorrect issues due to this, except for incorrect JDBC metadata for such columns.

Issue Links

• relates to: DERBY-1742 SYSTEMALIAS column of type BOOLEAN in SYS.SYSALIASES is created with the incorrect maximun length of 0