Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <27771156.1184265424462.JavaMail.jira@brutus>
Date: Thu, 12 Jul 2007 11:37:04 -0700 (PDT)
From: "Mike Matrigali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-2931) jdbcapi/ConcurrencyTest not able to
 drop table in soft upgrade mode
In-Reply-To: <21649299.1184245268048.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-2931?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali updated DERBY-2931:
----------------------------------

    Attachment: derby2931.diff

derby2931.diff is proposed fix for derby2931 for the trunk.  Mostly comment=
 changes and fixes the format id version used for accessing old format Heap=
's,
it was incorrectly using the new one.  To reproduce you need to create pre-=
10.3 base table, and then in 10.3 somehow access that table not from cache.=
 =20
Easiest is to shut down and startup again in a soft upgrade db, but bug wou=
ld also happen if you managed to access enough tables to age out the create=
d table from the container cache. =20

So far I have run upgrade tests against fix applied to 10.3 branch and hand=
 tested the change against the repro case that Knut describes in this JIRA =
entry.


> jdbcapi/ConcurrencyTest not able to drop table in soft upgrade mode
> -------------------------------------------------------------------
>
>                 Key: DERBY-2931
>                 URL: https://issues.apache.org/jira/browse/DERBY-2931
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.1.1
>         Environment: Soft upgrade=20
>            Reporter: =C3=98ystein Gr=C3=B8vlen
>            Assignee: Mike Matrigali
>            Priority: Blocker
>         Attachments: derby2931.diff
>
>
> 1. Created at database system/wombat with ij version 10.2
> 2. Ran jdbcapi/ConcurrencyTest with same current directory. All test case=
s but the first test fail with:
> 30) testTruncateDuringScan(org.apache.derbyTesting.functionTests.tests.jd=
bcapi.ConcurrencyTest)junit.framework.ComparisonFailure: 'drop table t1' fa=
iled with unexpected SQL State expected:<[42Y55]> but was:<[XSDA7]>
>         at org.apache.derbyTesting.functionTests.tests.jdbcapi.SURDataMod=
elSetup.createDataModel(SURDataModelSetup.java:70)
>         at org.apache.derbyTesting.functionTests.tests.jdbcapi.SURDataMod=
elSetup.createDataModel(SURDataModelSetup.java:125)
>         at org.apache.derbyTesting.functionTests.tests.jdbcapi.Concurrenc=
yTest.setUp(ConcurrencyTest.java:54)
>         at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCas=
e.java:88)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>         at junit.extensions.TestSetup.run(TestSetup.java:25)
>         at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.=
java:57)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>         at junit.extensions.TestSetup.run(TestSetup.java:25)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>         at junit.extensions.TestSetup.run(TestSetup.java:25)
>         at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.=
java:57)

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.