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 Thu, 16 Aug 2007 15:55:15 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

The comment on the change is:
There were typos in page. It should say current compilation schema's collation.

------------------------------------------------------------------------------
  
  2)<column definition> (of character string type) SQL spec Section 11.1 <schema
definition>, General Rule 3 specifies that the character set associated with schema is
used as the default character set for all <column definitions>. Based on this, character
columns in user tables will have USER character set associated with them and hence collation
type of UCS_BASIC/TERRITORY_BASED. The collation derivation will be implicit. 
  
- 3)<character string type> (SQL spec section 6.1 <data type> Syntax Rule 3b and
16) - Rule 3b says that collation type of character string type is the character set's collation
AND rule 16 says that if <character string type> is not contained in a <column definition>,
then an implementation-defined character set is associated with the <character string type>.
We define Derby's implementation-defined character set for such <character string type>
to be current schema's character set. The collation derivation will be implicit. 
+ 3)<character string type> (SQL spec section 6.1 <data type> Syntax Rule 3b and
16) - Rule 3b says that collation type of character string type is the character set's collation
AND rule 16 says that if <character string type> is not contained in a <column definition>,
then an implementation-defined character set is associated with the <character string type>.
We define Derby's implementation-defined character set for such <character string type>
to be current compilation schema's character set. The collation derivation will be implicit.

  
- 4)<cast specification> Section 6.12 Syntax Rule 10 says that if the target data type
of CAST is character string type, then collation type of result character string of CAST specification
is the collation of the character set of the target data type. Based on 3) above, that will
be the collation of the current schema's character set. The collation derivation will be implicit.

+ 4)<cast specification> Section 6.12 Syntax Rule 10 says that if the target data type
of CAST is character string type, then collation type of result character string of CAST specification
is the collation of the character set of the target data type. Based on 3) above, that will
be the collation of the current compilation schema's character set. The collation derivation
will be implicit. 
  
  5)Result character string types from UPPER, LOWER, TRIM(LTRIM, RTRIM), SUBSTR will have
the same collation as their operand. This comes from SQL spec Section 6.29 <string value
function> Syntax Rules 8, 8, 11d, 4 respectively). The collation derivation will be implicit.

  
- 6)CHAR, VARCHAR functions do not look like they are defined in the SQL spec. Their behavior
can be defined as similar to CAST ie, the result character string of CHAR/VARCHAR will have
the same collation as current schema's character set. The collation derivation will be implicit.
+ 6)CHAR, VARCHAR functions do not look like they are defined in the SQL spec. Their behavior
can be defined as similar to CAST ie, the result character string of CHAR/VARCHAR will have
the same collation as current compilation schema's character set. The collation derivation
will be implicit.
  
  6a) XMLSERIALIZE (defined in SQL Standard Part 14) has the declared type of the explicit
character type in the function and thus falls under the rules defined in 3).
  

Mime
View raw message