Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-50

getMaxColumnNameLength() database metadata function returns incorrect value.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: 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.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: