Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <5257225.1149579331121.JavaMail.jira@brutus>
Date: Tue, 6 Jun 2006 07:35:31 +0000 (GMT+00:00)
From: "Knut Anders Hatlen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-655) getImportedKeys returns duplicate
 rows in some cases
In-Reply-To: <299741707.1130429937789.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-655?page=comments#action_12414920 ] 

Knut Anders Hatlen commented on DERBY-655:
------------------------------------------

Mamta A. Satoor wrote:

> 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.

Does this mean that the upgrade test is going to fail until 10.1.3 is
released and the jars checked into the repository? If that's the case,
I think we should update the upgrade test canon temporarily now and
revert it once 10.1.3 is out. Ole's tinderbox test has failed since
the check-in of this patch.

> 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