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:51:07 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:

  4)This item is related to item 3. When DVF gets called by store to create right DVD for
given formatid and collation type, for formatids associated with character datatypes, it will
first create the base character datatype class which is say SQLChar. Then it will call getValue
method on the DVD with the RuleBasedCollator corresponding to the collation type as the parameter.
(This RuleBasedCollator will be null for UCS_BASIC collation). The getValue method will return
SQLChar or CollatorSQLChar depending on whether RuleBasedCollator is null or not. getValue
is the new method which needs to be added to the interface StringDataValue.
+ 5)Check if any code needs to go in for sorter. Not sure if this falls under Language or
Store section. Mike pointed out that Derby has some template code specific to sorter.
  1)Add tests for this feature. This a broad umbrella task but I do want to mention 3 specific
tests that we should be testing
@@ -108, +110 @@

  e)Make sure that a soft-upgraded pre-10.3 database continues to work with pre-10.3 release,
ie the store level column metadata structure should remain unchanged. This ties in with item
1) under Store section above.
  f)Add a test case for hard-upgrade of pre-10.3 database. This will cause a change in store
level column metadata structure. This ties in with item 1) under Store section above.
+ g)Add tests for sorts that can fit in memory and the sorts that have to spill over to disk.
It will be good to make sure that correction collation get used for them.
  Metadata query changes

View raw message