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

Support ALTER DATABASE to change collation

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • SQL, Store
    • Normal

    Description

      DERBY-1748 added the ability to control the collation of the database during database creation, but leaves users with existing databases with no way to upgrade their databases. In the case of my company, we have many Derby deployments in the field in production, and dropping and recreating the database during upgrade is not possible (or acceptable).

      Similar to MySQL, Derby should support ALTER DATABASE to change the default collation of a database. For reference, the MySQL syntax is:

      ALTER

      {DATABASE | SCHEMA}

      [db_name]
      alter_specification ...

      alter_specification:
      [DEFAULT] CHARACTER SET [=] charset_name

      [DEFAULT] COLLATE [=] collation_name

      I would suggest that this syntax is perfectly acceptable, and should be adopted by Derby.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-6310 NLS SESSION SORT

          • Major - Major loss of function.
          • Open
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-2856 allow change of territory/collation

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

              Unassigned Unassigned
              brettw Brett Wooldridge
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: