Derby
  1. Derby
  2. DERBY-1745

System catalog columns of type BIGINT and INT created with incorrect precision of zero.

    Details

    • Type: Task Task
    • Status: Open
    • Priority: Minor 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
    • Fix Version/s: None
    • Component/s: SQL
    • Urgency:
      Normal

      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

          Activity

          Gavin made changes -
          Workflow jira [ 12382197 ] Default workflow, editable Closed status [ 12801785 ]
          Mamta A. Satoor made changes -
          Labels derby_triage10_11
          Knut Anders Hatlen made changes -
          Issue Type Bug [ 1 ] Task [ 3 ]
          Urgency Normal
          Mike Matrigali made changes -
          Component/s SQL [ 11408 ]
          Daniel John Debrunner made changes -
          Field Original Value New Value
          Link This issue relates to DERBY-1742 [ DERBY-1742 ]
          Daniel John Debrunner created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Daniel John Debrunner
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development