[
https://issues.apache.org/jira/browse/DERBY-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513678
]
Knut Anders Hatlen commented on DERBY-2896:
-------------------------------------------
I haven't followed this discussion closely, but I'd just mention that before
you port the fix to 10.3, you might want to have a look at
http://wiki.apache.org/db-derby/MetadataUpgrade, the section about Maintenance
and Point Releases in particular. The changes in metadata.properties will not
be picked up when you upgrade from 10.3.1.x to 10.3.2.x. I don't know if that's
a problem, but you may have to do something more exotic to make it work in that
scenario.
> 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.
