[ http://issues.apache.org/jira/browse/DERBY-655?page=all ]
Mamta A. Satoor updated DERBY-655:
----------------------------------
Attachment: Derby655GetImportedKeysPatch1CodelineTrunk.txt
I have attached the patch for the main codeline to this JIRA entry as
Derby655GetImportedKeysPatch1CodelineTrunk.txt.
The upgrade test Upgrade_10_1_10_2 is not included in this patch because the
patch submitted for 10.1 first needs to go in and then the upgrade test will
give the correct master diff. Without the 10.1 patch in, the 10.1 database is
getting created with duplicate logical conglomerateids and hence, after the
upgrade to 10.2, the database still contains duplicate rows and hence incorrect
results. Once the patch for 10.1 goes in, the newly created 10.1 db will not
have duplicate logical conglomerateids. The part 2 of the solution for this
JIRA entry is not yet worked on. The part 2 is supposed to take care of
duplicate logical conglomerate ids when a database is upgraded.
Note to the committers : there are patches that need to be committed, one for
10.1 codeline and another for main codeline.
> 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,
> 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
