db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-655) getImportedKeys returns duplicate rows in some cases
Date Tue, 06 Jun 2006 16:27:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-655?page=all ]

Mamta A. Satoor updated DERBY-655:
----------------------------------

    Attachment: Derby655GetImportedKeysPatch1CodelineTrunkUpgradeTest.txt

The part I of the fix has gone into all the 3 codelines but the upgrade test fails with duplicate
row because the 10.1 jar used by the upgrade test does not yet have those changes. 

Seems like the 10.1 jar will get updated only when 10.1.3 wil be ready and hence I am attaching
a patch (Derby655GetImportedKeysPatch1CodelineTrunkUpgradeTest.txt) with the duplicate row
for the upgrade test until 10.1.3 jars are checked in. Can a committer please check in this
change?

> getImportedKeys returns duplicate rows in some cases
> ----------------------------------------------------
>
>          Key: DERBY-655
>          URL: http://issues.apache.org/jira/browse/DERBY-655
>      Project: Derby
>         Type: Bug

>   Components: SQL
>     Versions: 10.2.0.0
>  Environment: Sun JDK 1.4.2, Windows XP
>     Reporter: Deepa Remesh
>     Assignee: Mamta A. Satoor
>  Attachments: Derby655GetImportedKeysPatch1.txt, Derby655GetImportedKeysPatch1Codeline101.txt,
Derby655GetImportedKeysPatch1CodelineTrunk.txt, Derby655GetImportedKeysPatch1CodelineTrunkUpgradeTest.txt,
Derby655GetImportedKeysPatch2Codeline101.txt, Derby655GetImportedKeysStat1.txt, bigdb.sql,
keys.java, keys_test.zip, smalldb.sql
>
> I have a database with a large number of tables.  I get duplicate rows when I call DatabaseMetaData.getImportedKeys
for a particular table. However, if I create the same table with same number of foreign keys
in another database (which has fewer number of tables), then getImportedKeys returns me the
correct number of rows. This error seems to happen only when the database has a large number
of tables. I will attach a repro for this shortly. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message