Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Thu, 22 Mar 2007 18:12:59 -0000
Message-ID: <20070322181259.28297.82771@eos.apache.osuosl.org>
Subject: [Db-derby Wiki] Update of "BuiltInLanguageBasedOrderingDERBY-1478" by
 MamtaSatoor

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

------------------------------------------------------------------------------
  '''Table of Contents'''
  [[TableOfContents(2)]]
+ 
+ NOTE : This page is currently collection of all the known line items in a random order. Once I have them all jotted down, I will then organize them into sub-sections and then send an email to the list. In the mean time, I appreciate people on the list going through these lineitems as they are listed and asking questions because it points out areas that I might not have thought of. 
  
  == Design proposals ==
  In 10.3, a user might create a table with CHAR datatypes along with other datatypes. The task at hand is if the user has asked for territory based collation, then we want these CHAR datatypes to collate differently than the CHAR datatypes that exist today in 10.2 And if the user hasn't requested territory based collation, then we want these CHAR datatypes to collate the way they do in 10.2 today. So, in short, the CHAR datatype in 10.3 will have different collation behavior depending on what user has requested. But as far as the user is concerned, they are just SQL CHAR datatypes and not new SQL datatypes.