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:41:08 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

------------------------------------------------------------------------------
  
  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 upgraded
to 10.3 and for new 10.3 databases with default collatoin(UCS_BASIC), 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 their store metadata. A new version would be used in Store
for structure of column level metadata if the newly created 10.3 database has asked for territory
based collation. In other words, information about collate will be kept in Store column level
metadata only if we are working with a 10.3 newly created database with territory based collation.
This approach will make sure that we do not have to do an on-disk store metadata upgrade when
upgrading a pre-10.3 database to 10.3 version.
+ 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
+ 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.
  
@@ -102, +104 @@

  c)CREATE VIEW should have collation type UCS_BASIC/TERRIOTRY_BASED assocatied with it's
character columns. The exact collation will be determined by what is the value of the COLLATION
attribute. This is same as what would happen for CREATE TABLE. Have a test for global temporary
tables with character colums too.
  
  d)Write a test case for store btree recovery which will ensure that Locale info in correctly
set in DVF by BasicDatabase during recovery case.
+ 
+ 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.
  
  Metadata query changes
  

Mime
View raw message