db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5179) Support ALTER DATABASE to change collation
Date Thu, 07 Apr 2011 07:30:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016732#comment-13016732

Knut Anders Hatlen commented on DERBY-5179:

I've linked this report to DERBY-2856, which requests the same functionality. That report
isn't limited to a specific syntax/interface, so the two reports aren't strictly duplicates,
but we'd probably only fix one of them.

Derby typically uses URL attributes as the interface when performing database-wide transformations.
Something like "jdbc:derby:db;newTerritory=en_US;newCollation=TERRITORY_BASED" would follow
the same pattern as reencrypting the database.

> 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
> 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_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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message