db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2724) Set correct collation type and derivation for result character string types from CURRENT ISOLATION, CURRENT_USER, SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID.
Date Fri, 01 Jun 2007 19:02:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor updated DERBY-2724:
-----------------------------------

    Description: 
As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478,
assign correct collation type for esult character string types from CURRENT ISOLATION, CURRENT_USER,
SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID. The rule as copied from the wiki
page is as follows
9)For CURRENT_USER, SESSION_USER, SYSTEM_USER, SQL spec Section 6.4 Syntax Rule 4 says that
their collation type is the collation of character set SQL_IDENTIFIER. In Derby's case, that
will mean, the collation of these functions will be UCS_BASIC. The collation derivation will
be implicit. 

10)CURRENT ISOLATION, CURRENT SCHEMA and CURRENT SQLID seem to be Derby specific functions,
I didn't find them in the SQL spec. But in order to match their behavior with the other functions
covered in 9) above, their return character string type's collation will be the collation
of character set SQL_IDENTIFIER. The collation derivation will be implicit. 


  was:
As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478,
assign correct collation type for esult character string types from CURRENT_USER, SESSION_USER,
SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID. The rule as copied from the wiki page is as
follows
9)For CURRENT_USER, SESSION_USER, SYSTEM_USER, SQL spec Section 6.4 Syntax Rule 4 says that
their collation type is the collation of character set SQL_IDENTIFIER. In Derby's case, that
will mean, the collation of these functions will be UCS_BASIC. The collation derivation will
be implicit. 

10)CURRENT SCHEMA and CURRENT SQLID seem to be Derby specific functions, I didn't find them
in the SQL spec. But in order to match their behavior with the other functions covered in
9) above, their return character string type's collation will be the collation of character
set SQL_IDENTIFIER. The collation derivation will be implicit. 


        Summary: Set correct collation type and derivation for result character string types
from CURRENT ISOLATION, CURRENT_USER, SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT
SQLID.  (was: Set correct collation type and derivation for result character string types
from CURRENT_USER, SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID.)

CURRENT ISOLATION is another Derby specific function that returns a character string and I
think the collation type of that string should be same what we decided for CURRENT SCHEMA
and CURRENT SQLID which is UCS_BASIC. I will go ahead and update the wiki page to include
CURRENT ISOLATION along with CURRENT SCHEMA and CURRENT SQLID.

> Set correct collation type and derivation for result character string types from CURRENT
ISOLATION, CURRENT_USER, SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2724
>                 URL: https://issues.apache.org/jira/browse/DERBY-2724
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>
> As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478,
assign correct collation type for esult character string types from CURRENT ISOLATION, CURRENT_USER,
SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID. The rule as copied from the wiki
page is as follows
> 9)For CURRENT_USER, SESSION_USER, SYSTEM_USER, SQL spec Section 6.4 Syntax Rule 4 says
that their collation type is the collation of character set SQL_IDENTIFIER. In Derby's case,
that will mean, the collation of these functions will be UCS_BASIC. The collation derivation
will be implicit. 
> 10)CURRENT ISOLATION, CURRENT SCHEMA and CURRENT SQLID seem to be Derby specific functions,
I didn't find them in the SQL spec. But in order to match their behavior with the other functions
covered in 9) above, their return character string type's collation will be the collation
of character set SQL_IDENTIFIER. The collation derivation will be implicit. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message