db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "BuiltInLanguageBasedOrderingDERBY-1478" by MamtaSatoor
Date Sat, 07 Apr 2007 07:10:25 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by MamtaSatoor:
http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478

------------------------------------------------------------------------------
  == Outstanding items ==
  '''[[GetText(Language changes)]]'''
  
- 1)When a character column is added using CREATE TABLE/ALTER TABLE, make sure that the correct
collate type is populated in the TypeDescriptor's scale field in the SYS.SYSCOLUMNS table.
In order to do this, CREATE TABLE/ALTER TABLE need to get their schema descriptor's collation
type. The collation type of the schema descriptor will decide the collation type of the character
columns defined in CREATE TABLE/ALTER TABLE. This comes from item 2 under Collation Determination
section on this page. ALTER TABLE changes should work for both ADD COLUMN and MODIFY character
column increase length.
+ 1)When a character column is added using CREATE TABLE/ALTER TABLE, make sure that the correct
collate type is populated in the TypeDescriptor's scale field in the SYS.SYSCOLUMNS table.
In order to do this, CREATE TABLE/ALTER TABLE need to get their schema descriptor's collation
type. The collation type of the schema descriptor will decide the collation type of the character
columns defined in CREATE TABLE/ALTER TABLE. This comes from item 2 under Collation Determination
section on this page. ALTER TABLE changes should work for both ADD COLUMN and MODIFY character
column increase length. Part of the code changes required for this item has gone in revision
526385 as part of DERBY-2530. Some more language changes and some store changes need to go
in for this task to finish. Those changes involve passing the collation type from language
to the store layer as part of CREATE TABLE and ALTER TABLE. Mike is planning to look into
that.
  
  2)WorkHorseForCollatorDatatypes should override all the collation related methods so that
it uses the non-default Collator. All the non-default-collation-sensitive classes have an
instance of WorkHorseForCollatorDatatypes which is used to call the collation related methods.
This ensures that these collation related methods are implemented in one central place rather
than in all the collation-sensitive classes. 
  

Mime
View raw message