db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2336) Enable collation based ordering for CHAR data type.
Date Wed, 07 Mar 2007 00:01:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478645

Mike Matrigali commented on DERBY-2336:

Logically  it seems like at boot time what we want is to set a static variable in one or a
few datatypes (the new datatypes that mamta just described above - I assume one below CHAR,
VARCHAR, and CLOB)  to store the collation info and then
that info would be efficiently available always to the those datatypes. The compiler and the
format id's make it so that the extra path code
only happens in the new datatypes.  It seems like anything that requires extra passed info
on every 
datatype creation is unnecessary overhead, until we really want to support different collations
at less than a db unit (ie. datavalue, columns, 
and/or table).

 Is there anyway we could get the datatype system to support something like that?  

> 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:
>            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.

View raw message