[
https://issues.apache.org/jira/browse/DERBY-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-2595.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
Thanks, Jørgen! Committed revision 533175.
I noticed that the old code only committed the transaction once after dropping
all the foreign keys, whereas the patch would commit once for each table. I
changed back to the old behaviour before committing.
> junit tests uses getExportedKeys with table name null
> -----------------------------------------------------
>
> Key: DERBY-2595
> URL: https://issues.apache.org/jira/browse/DERBY-2595
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.2.2.0
> Reporter: Jørgen Løland
> Assigned To: Jørgen Løland
> Fix For: 10.3.0.0
>
> Attachments: DERBY-2595-1.diff, DERBY-2595-1.stat
>
>
> org.apache.derbyTesting.junit.JDBC.dropSchema uses
> DatabaseMetadata#getExportedKeys with null as table name. This is not allowed
> according to java.sql.DatabaseMetaData.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
