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 Fri, 26 May 2006 04:38:33 GMT
     [ http://issues.apache.org/jira/browse/DERBY-655?page=all ]

Mamta A. Satoor updated DERBY-655:

    Attachment: Derby655GetImportedKeysPatch1.txt

Attaching patch for the first part of the solution, which is to generate unique logical conglomerates
for duplicate indexes. Also, I tried my patch against DERBY-1343 and this patch takes care
of part 1 of that bug too. 
Derby655GetImportedKeysPatch1.txt is the actual patch and Derby655GetImportedKeysStat1.txt
is svn stat output for the patch.

This patch is for 10.0 codeline. Same fix needs to be put in to all the subsequent codelines.
Do I need to submit separate patches for 10.1 and 10.2 codelines? Can a commiter see if the
patch looks good and can be checked in?

> 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