[
https://issues.apache.org/jira/browse/DERBY-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513395
]
Stan Bradbury commented on DERBY-2896:
--------------------------------------
Database metadata calls are used a lot to provide database independence and
without this problem fixed TERRITORY_BASED collation (other than the default)
will not be able to be used in these systems. This preoblem is certainly a
Blocker for this feature but should the release be blocked? There is a
proposed fix for the problem and I would like to see this implemented ASAP.
I propose that the 10.3.1.2 release go forward with this problem well
documented and that an official release (10.3.2.x) be created within 4-6 weeks
that corrects this and any other serious problems that are reported during this
'shake-down' period.
What say you?
> 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.
