[
https://issues.apache.org/jira/browse/DERBY-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478832
]
Mike Matrigali commented on DERBY-2336:
---------------------------------------
Dan's solution seems good - let the datatype system encapsulate everything.
The details I don't understand are:
1) How does Database (BasicDatabase) get set up in the runtime recovery case,
we need the collation stuff before the database has been
recovered - I think in the current system it only gets initialized later.
Or in recovery case is store making the DatavalueFactory.setLocale()
call?
2) Is it ok for store to boot DataValueFactory, before the database has been
recovered?
I think this is ok, that a lot of work has been done to move toward this,
are we there now?
> Enable collation based ordering for CHAR data type.
> ---------------------------------------------------
>
> Key: DERBY-2336
> URL: https://issues.apache.org/jira/browse/DERBY-2336
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.3.0.0
> Reporter: Mamta A. Satoor
> Attachments: DERBY_LocalFinder_CodeCleanup_diff_V01.txt,
> DERBY_LocalFinder_CodeCleanup_stat_V01.txt
>
>
> I am breaking down the Parent task DERBY-1478 (Add built in language based
> ordering and like processing to Derby) into multiple sub tasks. One of them
> is to concentrate on enabling the collation based ordering on (hopefully the
> simplest of all the character data types) CHAR data type. This task in itself
> might need subtasks if it is later found that it can be subdivided into
> multiple smaller steps.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
