db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5179) Support ALTER DATABASE to change collation
Date Tue, 16 Aug 2011 09:54:27 GMT

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

Kristian Waagan commented on DERBY-5179:

Some databases support specifying collations on a per query basis. I haven't researched this,
but I assume this applies for SELECTs only? I have no idea how this functionality work with
respect to "collated indexes".
I've also seen examples where you can modify collations using SQL.

> 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