You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Brett Wooldridge (JIRA)" <ji...@apache.org> on 2011/04/07 03:04:05 UTC
[jira] [Created] (DERBY-5179) Support ALTER DATABASE to change
collation
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, 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5179) Support ALTER DATABASE to change
collation
Posted by "Brett Wooldridge (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (DERBY-5179) Support ALTER DATABASE to change
collation
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (DERBY-5179) Support ALTER DATABASE to change
collation
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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 {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
[jira] [Commented] (DERBY-5179) Support ALTER DATABASE to change
collation
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ 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 {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