db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-2534) Add new api "public StringDataValue getValue(RuleBasedCollator)" on StringDataValue. This method will return either the base DVDs for char datatypes or it will return collation sensitive DVD for char datatypes.
Date Mon, 09 Apr 2007 07:51:32 GMT

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

Mamta A. Satoor reassigned DERBY-2534:
--------------------------------------

    Assignee: Mamta A. Satoor

> Add new api "public StringDataValue getValue(RuleBasedCollator)" on StringDataValue.
This method will return either the base DVDs for char datatypes or it will return collation
sensitive DVD for char datatypes.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2534
>                 URL: https://issues.apache.org/jira/browse/DERBY-2534
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>         Assigned To: Mamta A. Satoor
>         Attachments: DERBY2534_getValue_On_StringDataValue_v1_diff.txt, DERBY2534_getValue_On_StringDataValue_v1_stat.txt
>
>
> In Derby 10.3, the collation of char datatypes can be different depending on what kind
of collation is requested by the user at the database create time through the optional JDBC
url attribute COLLATION. The collation type associated with the DTD will determine which kind
of DVD needs to be generated. (Note that, irrespective of what collation is used, the format
id of the char datatypes remain same.) In order to support this behavior of generating the
base DVD or the collation sensitive DVD for character datatypes, we need to add a new api
to StringDataValue which will look as follows
> 	/**
> 	 * Gets either SQLChar/SQLVarchar/SQLLongvarchar/SQLClob(base classes) or 
> 	 * CollatorSQLChar/CollatorSQLVarchar/CollatorSQLLongvarch/CollatorSQLClob
> 	 * (subclasses). Whether this method returns the base class or the subclass 
> 	 * depends on the value of the RuleBasedCollator. If RuleBasedCollator is 
> 	 * null, then the object returned would be baseclass otherwise it would be 
> 	 * subcalss.
> 	 */
> 	public StringDataValue getValue(RuleBasedCollator collatorForComparison);

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message