You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2007/05/29 22:17:15 UTC

[jira] Created: (DERBY-2722) Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions

Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
-------------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-2722
                 URL: https://issues.apache.org/jira/browse/DERBY-2722
             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 results of CHAR, VARCHAR and XMLSERIALIZE functions. The rule as copied from the wiki page is as follows
6)CHAR, VARCHAR and XMLSERIALIZE 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/XMLSERIALIZE will have the same collation as current schema's character set. 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.


[jira] Closed: (DERBY-2722) Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor closed DERBY-2722.
----------------------------------


> Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2722
>                 URL: https://issues.apache.org/jira/browse/DERBY-2722
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt, DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_stat.txt
>
>
> As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478, assign correct collation type for results of CHAR, VARCHAR and XMLSERIALIZE functions. The rule as copied from the wiki page is as follows
> 6)CHAR, VARCHAR and XMLSERIALIZE 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/XMLSERIALIZE will have the same collation as current schema's character set. 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.


[jira] Reopened: (DERBY-2722) Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor reopened DERBY-2722:
------------------------------------


Army found following issue with the test contributed by me for XML type

Army wrote:
> +
> +      s.executeUpdate("set schema APP");
> +      checkLangBasedQuery(s, "SELECT XMLSERIALIZE(x as CHAR(10)) " +
> +             " FROM xmlTable, SYS.SYSTABLES WHERE " +
> +                     " XMLSERIALIZE(x as CHAR(10)) = TABLENAME",
> +                     null);

Just for the record, I think use of XMLSERIALIZE here will fail if the test
classpath does not include the required Xalan/JAXP classes (ex. Sun jdk15 with
no external XML jars).  It might be good to wrap this particular test inside of an

    if (XML.classpathMeetsXMLReqs())
     ....

where "XML" is junit/XML.java.  I think that's all that would be needed, though
I haven't actually tried it out...

> Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2722
>                 URL: https://issues.apache.org/jira/browse/DERBY-2722
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt, DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_stat.txt
>
>
> As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478, assign correct collation type for results of CHAR, VARCHAR and XMLSERIALIZE functions. The rule as copied from the wiki page is as follows
> 6)CHAR, VARCHAR and XMLSERIALIZE 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/XMLSERIALIZE will have the same collation as current schema's character set. 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.


[jira] Resolved: (DERBY-2722) Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor resolved DERBY-2722.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0

> Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2722
>                 URL: https://issues.apache.org/jira/browse/DERBY-2722
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt, DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_stat.txt
>
>
> As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478, assign correct collation type for results of CHAR, VARCHAR and XMLSERIALIZE functions. The rule as copied from the wiki page is as follows
> 6)CHAR, VARCHAR and XMLSERIALIZE 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/XMLSERIALIZE will have the same collation as current schema's character set. 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.


[jira] Commented: (DERBY-2722) Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500444 ] 

Mamta A. Satoor commented on DERBY-2722:
----------------------------------------

Commited fix for XML test as part of revision 543209 with following commit comments
"DERBY-2722
Before making call to XMLSERIALIZE, we should check if the classpath includes the required Xalan/JAXP classes. Otherwise the test will fail with jvms, where these classes can't be found.
"

> Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2722
>                 URL: https://issues.apache.org/jira/browse/DERBY-2722
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt, DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_stat.txt
>
>
> As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478, assign correct collation type for results of CHAR, VARCHAR and XMLSERIALIZE functions. The rule as copied from the wiki page is as follows
> 6)CHAR, VARCHAR and XMLSERIALIZE 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/XMLSERIALIZE will have the same collation as current schema's character set. 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.


[jira] Resolved: (DERBY-2722) Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor resolved DERBY-2722.
------------------------------------

    Resolution: Fixed

> Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2722
>                 URL: https://issues.apache.org/jira/browse/DERBY-2722
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt, DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_stat.txt
>
>
> As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478, assign correct collation type for results of CHAR, VARCHAR and XMLSERIALIZE functions. The rule as copied from the wiki page is as follows
> 6)CHAR, VARCHAR and XMLSERIALIZE 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/XMLSERIALIZE will have the same collation as current schema's character set. 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.


[jira] Updated: (DERBY-2722) Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Attachment: DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_stat.txt
                DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt

Committed attached patch DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt with revision 543183. The commit comments are as follows

DERBY-2722
Committing changes which will make sure that we set the collation to current schema's collation for the return character string from XMLSERIALIZE. Don't have to make any changes for CHAR and VARCHAR functions because these functions gets translated into CAST by the parser and I have already checked in changes for the result of CAST to have the collation of current schema.


> Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2722
>                 URL: https://issues.apache.org/jira/browse/DERBY-2722
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt, DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_stat.txt
>
>
> As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478, assign correct collation type for results of CHAR, VARCHAR and XMLSERIALIZE functions. The rule as copied from the wiki page is as follows
> 6)CHAR, VARCHAR and XMLSERIALIZE 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/XMLSERIALIZE will have the same collation as current schema's character set. 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.


[jira] Closed: (DERBY-2722) Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions

Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor closed DERBY-2722.
----------------------------------


> Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2722
>                 URL: https://issues.apache.org/jira/browse/DERBY-2722
>             Project: Derby
>          Issue Type: New Feature
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_diff.txt, DERBY2722_set_collation_for_xmlserialize_char_varchar_functions_v1_stat.txt
>
>
> As per the wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478, assign correct collation type for results of CHAR, VARCHAR and XMLSERIALIZE functions. The rule as copied from the wiki page is as follows
> 6)CHAR, VARCHAR and XMLSERIALIZE 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/XMLSERIALIZE will have the same collation as current schema's character set. 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.