db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-655) getImportedKeys returns duplicate rows in some cases
Date Fri, 26 May 2006 07:49:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-655?page=comments#action_12413392 ] 

Satheesh Bandaram commented on DERBY-655:

Submitted this patch. Normally would have asked if you really have an itch to see this fix
in 10.0, but since this problem potentially leaves system tables in confusing state, I have
merged this into 10.0.

Sending        java\engine\org\apache\derby\impl\sql\execute\CreateIndexConstantAction.java
Sending        java\testing\org\apache\derbyTesting\functionTests\master\DerbyNet\metadata.out
Sending        java\testing\org\apache\derbyTesting\functionTests\master\metadata.out
Sending        java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\metadata.java
Transmitting file data ....
Committed revision 409580.

> 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:
>  Environment: Sun JDK 1.4.2, Windows XP
>     Reporter: Deepa Remesh
>     Assignee: Mamta A. Satoor
>  Attachments: Derby655GetImportedKeysPatch1.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:
For more information on JIRA, see:

View raw message