[
https://issues.apache.org/jira/browse/DERBY-5179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Wooldridge updated DERBY-5179:
------------------------------------
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.
was:
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, they 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.
> 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 {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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
