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 07:18:22 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)Set the correct collation type for return parameter from user defined functions when the
return type is a character string type.
+ 
+ 4)Some of the numbered Rules in Collation Derivation sections on this page need to be discussed
to make sure we are setting the collation right. This will make sure that in future, when
we do start to support different collation for different user schemas, things don't fall apart.
The discussion has been started by Dan in couple threads (http://www.nabble.com/Collation-and-parameter-markers-%28-%29-tf3866040.html#a10952369
and http://www.nabble.com/Collation-and-string-literals-limitation-in-SQL-standard--tf3868448.html#a10959872).
  '''[[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
@@ -120, +123 @@

  
  h2)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=UCS_BASIC';
  
- h3)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=TERRITORY_BASED';
- 
- h4)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=CUSTOM_COLLATION';
//invalid value for collation attribute
+ h3)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=CUSTOM_COLLATION';
//invalid value for collation attribute
  
- h5)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=TERRITORY_BASED;collation=TERRITORY_BASED';//give
same value twice
+ h4)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=TERRITORY_BASED;collation=TERRITORY_BASED';//give
same value twice
  
- h6)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=TERRITORY_BASED;collation=UCS_BASIC';//give
2 different values. The last value should get picked
+ h5)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=TERRITORY_BASED;collation=UCS_BASIC';//give
2 different values. The last value should get picked
  
- h7)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=UCS_BASIC;collation=TERRITORY_BASED';//same
as vi but valid values in different order
+ h6)connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=UCS_BASIC;collation=TERRITORY_BASED';//same
as vi but valid values in different order
  
- h8)After database create time, try to give collation attribute again. It should get quitely
ignored.
+ h7)After database create time, try to give collation attribute again. It should get quitely
ignored.
  connect 'jdbc:derby:c:/dellater/db1;create=true;territory=it;collation=TERRITORY_BASED';
  connect 'jdbc:derby:c:/dellater/db1;collation=UCS_BASIC';
  
- h9)connect 'jdbc:derby:c:/dellater/db1;create=true;collation=TERRITORY_BASED';//give collation
attribute w/o the locale attribute. We might need to discuss this to decide what happens.
Will put it under outstanding items.
- 
- h10)Connect to a pre-10.3 database in soft upgrade mode
+ h8)Connect to a pre-10.3 database in soft upgrade mode
  connect 'jdbc:derby:c:/dellater/db102';
  
- h11)Upgrade a pre-10.3 database
+ h9)Upgrade a pre-10.3 database
  connect 'jdbc:derby:c:/dellater/db102;upgrade=true';
  
  i)When adding tests for ALTER TABLE, try both add character column AND increase the length
of an existing character column.

Mime
View raw message