Description
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.
Attachments
Issue Links
- relates to
-
DERBY-2703 calling DatabaseMetaData.getColumns() with % for matching column character in a territory based collated db does not work in 1.4.2 jvms
-
- Closed
-
-
DERBY-2896 DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed.
-
- Closed
-
-
DERBY-1478 Add built in language based ordering and like processing to Derby
-
- Closed
-