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, 05 Jun 2007 06:46:41 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

------------------------------------------------------------------------------
  
  '''[[GetText(Answer)]]''' Mike, sorry, I forget the requirement for this one. Do we still
have a todo here?
  
- 3)Cleanup the new interface DTD.comparable to use isXXX methods rather than looking for
StoredFormatIds. DERBY-2569
- 
  '''[[GetText(Store changes)]]'''
  
  1)Store column level metadata for collate in Store. Store keeps a version number that describes
the structure of column level metadata. For existing pre-10.3 databases which get soft upgraded
to 10.3, the structure of column level metadata will remain same as 10.2 structure of column
level metadata, ie they will not include collate information in
@@ -185, +183 @@

  
  5)WorkHorseForCollatorDatatypes overrides 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. 
  
+ 6)Cleanedup the new interface DTD.comparable to use isXXX methods rather than looking for
StoredFormatIds. DERBY-2569
+ 
  '''[[GetText(Code Generation)]]'''
  
  1)At compile time, we make sure that the correct character class (ex SQLChar vs CollatorSQLChar)
is generated so at run time, we do not need to check what kind of Collator object need to
be used for character types. It is all handled at the code generation time and the appropriate
runtime methods (ex like method in SQLChar vs like method in WorkHorseForCollatorDatatypes)
get called at runtime. The changes for this went in as part of DERBY-2583.

Mime
View raw message