[
https://issues.apache.org/jira/browse/DERBY-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513643
]
Mamta A. Satoor commented on DERBY-2896:
----------------------------------------
Checked in fix for this bug in main with revision 557334. The commit changes
were as follows (Myrna, can I migrate this change to 10.3 codeline?)
DERBY-2896
Metadata calls getTables and getUDTs were failing when run from a user schema
in a territory based collated database.
The reason for it is that these metadata calls were not getting compiled in SYS
schema when they were executed from
a user schema. Metadata calls should always compile in SYS schema no matter
what the current schema might be. The
reason getTables was not getting compiled in SYS schema was because we were
trying to modify it's metadata sql on
the fly and then were compiling that modified sql in whatever the current
schema might be. I have changed the
metadata sql for getTables in metadata.properties so that we do not need to
modify it on the fly anymore. This will
allow getTables to follow the same codepath as other metadata queries which
will also ensure that the sql gets
compiled in SYS schema.
As for getUDTs, it was merely a coding bug that we didn't follow the same logic
as other metadata queries for it.
I have changed getUDTs implementation to follow the same codepath as other
metadata queries.
--This line, and those below, will be ignored--
M java/engine/org/apache/derby/impl/jdbc/metadata.properties
M java/engine/org/apache/derby/impl/jdbc/EmbedDatabaseMetaData.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/lang/CollationTest.java
> DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with
> SQLState 42818: Comparisions between CHAR and CHAR not allowed.
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2896
> URL: https://issues.apache.org/jira/browse/DERBY-2896
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.0.0, 10.3.1.0, 10.4.0.0
> Reporter: Daniel John Debrunner
> Assignee: Mamta A. Satoor
> Priority: Critical
> Attachments: Test2896.zip
>
>
> I tried adding DatabaseMetaDataTest.suite() to be run within CollationTest so
> that it would test DatabaseMetaData within a collated database.
> I had to fix one item in JDBC.dropSchema() where a string constant was being
> compared to a system column while not in a system schema,
> but with that fixed the next error hit was executing
> DatabaseMetaData.getTables().
> I will add the code to collation test with the use of DatabaseMetaDataTest
> commented out with this bug number.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
