db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6310) NLS SESSION SORT
Date Mon, 05 Aug 2013 18:32:47 GMT

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

Rick Hillegas updated DERBY-6310:

               Urgency: Normal  (was: Urgent)
    Bug behavior facts:   (was: Crash)
            Issue Type: Improvement  (was: Bug)

Changing this issue from Bug to Improvement. ALTER SESSION is not a Standard SQL statement.
However, the SQL Standard defines a statement with similar meaning (see part 2 of the Standard,
section 19.10 <set session collation statement>):

SET COLLATION <collation specification> [ FOR <character set specification list>

The SET COLLATION statement changes the collation used for ordering character data in queries
issued by the current session.

Right now Derby only lets you declare the collation for ALL user data in the database. This
declaration can only be made when the database owner creates the database. The declared collation
applies to all user data in all sessions. There is currently no way to change the collation
during the lifetime of the database.

This feature would be related to the ability to change the collation for the whole database:
> ----------------
>                 Key: DERBY-6310
>                 URL: https://issues.apache.org/jira/browse/DERBY-6310
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions:
>         Environment: Java 1.6 / 1.7, Derby
>            Reporter: Sebastian Ritter
> Migrating from Oracle missing SQL Statement:

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

View raw message