[
https://issues.apache.org/jira/browse/DERBY-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-1745:
--------------------------------------
Urgency: Normal
Issue Type: Task (was: Bug)
Triaged for 10.5.2.
The bug description says "This bug is here to investigate upgrade issues and
fix them if required." Changing issue type from Bug to Task.
> System catalog columns of type BIGINT and INT created with incorrect
> precision of zero.
> ---------------------------------------------------------------------------------------
>
> Key: DERBY-1745
> URL: https://issues.apache.org/jira/browse/DERBY-1745
> Project: Derby
> Issue Type: Task
> Components: SQL
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 10.2.1.6
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
