[
https://issues.apache.org/jira/browse/DERBY-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729780#comment-13729780
]
Rick Hillegas commented on DERBY-6310:
--------------------------------------
A crude workaround would be the following:
1) Create a temporary, in-memory database with the desired, alternative
collation.
2) In that database create a ForeignTableVTI against the original data. See
http://db.apache.org/derby/docs/10.10/publishedapi/jdbc4/org/apache/derby/vti/ForeignTableVTI.html
3) Then select from the ForeignTableVTI, using an ORDER BY clause. The data
will come back ordered according to the alternative collation.
4) Drop the temporary, in-memory database when you're done.
> NLS SESSION SORT
> ----------------
>
> Key: DERBY-6310
> URL: https://issues.apache.org/jira/browse/DERBY-6310
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.8.2.2
> Environment: Java 1.6 / 1.7, Derby 10.8.2.2
> Reporter: Sebastian Ritter
>
> Migrating from Oracle missing SQL Statement:
> ALTER SESSION SET NLS_SORT=binary
--
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
