Derby
  1. Derby
  2. DERBY-50

getMaxColumnNameLength() database metadata function returns incorrect value.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.2.0
    • Fix Version/s: 10.0.2.0
    • Component/s: JDBC
    • Labels:
      None
    • Environment:
      Generic issue. Was reproduced on Windows platform.

      Description

      Database Metadata function getMaxColumnNameLength() should return 30. It incorrectly returns 128. Derby restricts maximum column name length to be 30. Similarly, the following metadata functions also return incorrect values:

      getMaxCursorNameLength() = 18
      getMaxSchemaNameLength() = 30
      getMaxProcedureNameLength() = 128
      getMaxTableNameLength() = 128
      getMaxUserNameLength() = 30

      Note, there is some discussion in the derby developper list to increase maximum length of most identifiers to 128. If that happens, these metadata functions will need to be updated again. But for now, it these should return actual limits that are currently enforced.

        Activity

        Satheesh Bandaram created issue -
        Satheesh Bandaram made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 10.0.2.0 [ 10920 ]
        Resolution Fixed [ 1 ]
        Satheesh Bandaram made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Gavin made changes -
        Workflow jira [ 37985 ] Default workflow, editable Closed status [ 12800334 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Satheesh Bandaram
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development