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] Commented: (DERBY-2894) calling DatabaseMetaData.getColumns() with % for matching column character in a territory based collated db does not work in 1.4.2 jvms
Date Wed, 11 Jul 2007 06:19:04 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511667
] 

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

Can someone try this in sun142 environment because I just uncommented following from CollationTest2.runDERBY_2703
and didn't see any problems when running CollationTest2 with Sun jdk142
        //if (is142JVM())
          //  return;


$ which java
c:/p4clients/main/jdk142/bin/java.exe

> calling DatabaseMetaData.getColumns() with % for matching column character in a territory
based collated db does not work in 1.4.2 jvms
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2894
>                 URL: https://issues.apache.org/jira/browse/DERBY-2894
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>
> calling DatabaseMetaData.getColumns(null, "APP", "CUSTOMER", "%") returns no rows for
a valid APP.CUSTOMER table 
> in ibm142 and sun142 jvms, for databases created with territory based collation, fails
in all 3 cases we test in the 
> CollationTest2.java junit test. 
> Since this is a system catalog query I am surprised the result is affected at all by
collation, so there may be a derby bug 
> in the metadata routines, or elsewhere. Mamta, could you comment if you believe this
should work already - or if there 
> is more work to do in this area. 
> I will soon checkin a test case into the CollationTest2.java unit test that shows this.
For now I will either comment out the 
> entire test, or if I can figure out how to not run it on 142 I will do that.
> This issue was first reported as DERBY-2703 but it was reported as a subtask of DERBY-1478.
But since it really is a bug, I am re-reporting it at the top level so it can be tracked as
open bug.

-- 
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