db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5179) Support ALTER DATABASE to change collation
Date Fri, 28 Sep 2012 04:43:08 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor updated DERBY-5179:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
    
> Support ALTER DATABASE to change collation
> ------------------------------------------
>
>                 Key: DERBY-5179
>                 URL: https://issues.apache.org/jira/browse/DERBY-5179
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL, Store
>            Reporter: Brett Wooldridge
>              Labels: derby_triage10_10
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message