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 16:34:23 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

------------------------------------------------------------------------------
  
  6)CHAR, VARCHAR functions do not look like they are defined in the SQL spec. But based on
5) above, the result character string type's collation can be considered same as the first
argument's collation type if the first argument to CHAR/VARCHAR function is a character string
type. If the first argument is not character string type, then the result character string
of CHAR/VARCHAR will have the same collation as current schema's character set. The collation
derivation will be implicit.
  
+ '''[[GetText(Comment from Rick)]]''' The behavior will fall in SQL standard model if these
2 functions always returned a character string type with the collation of current schema's
character set. This will also be easier to implement and easier to explain to the user.
+ 
  7)For user defined functions' that return character string type, the return type's collation
will have the same collation as current schema's character set. The collation derivation will
be implicit. 
+ 
+ '''[[GetText(Comment from Dan)]]''' The "current schema's" character set, or the character
set of the schema the function is defined in? And if it's the current schema, is it current
at function definition time, or current when used?
+ 
  
  8)JDBC parameters (ie. ?) where the type of the parameter is a character type will have
the same collation as current schema's character set, based on 3) above.
  

Mime
View raw message