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 Tue, 03 Apr 2007 07:44:50 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

------------------------------------------------------------------------------
  their store metadata. For any conglomerate created in a 10.3 new database or a 10.3 hard
  upgraded database a new version would be used in Store to include information about the
collation for each column's metadata stored. This means that during upgrade, store needs to
change the sturcture of column level metadata to include collate information.
  
- 2)Currently, store uses Monitor to create DVD template rows. The logic of creating DVDs
using formatids should be factored out from Monitor into DataValueFactory. Talking in terms
of code, RowUtil.newClassInfoTemplate should call DVF.classFromIdentifier rather than Monitor.classFromIdentifier.
+ 2)Currently, store uses Monitor to create DVD template rows. The logic of creating DVDs
using formatids should be factored out from Monitor into DataValueFactory. Talking in terms
of code, RowUtil.newClassInfoTemplate should call DVF.classFromIdentifier rather than Monitor.classFromIdentifier.
There might be more apis in Monitor which can be/should be moved to DVF in order to keep all
data type related code in DVF.
  
  3)This item is related to item 2. With Derby 10.3, collation type will be the additional
metadata in store for each column. When store will call DVF to create DVD template row, it
will pass the formatids and the collation types. DVF will need to be able to assoicate the
correct Collator with the DVD for Char datatypes depending on the collation type. And in order
to find the correct Collator, DVF needs to know the locale of the database. This locale information
will be set on DVF using a new method on DVF called void setLocale(Locale). This call will
be made by BasicDatabase after DVF has finished booting and before store starts booting.
  

Mime
View raw message