Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 31 Aug 2012 10:55:07 +1100 (NCT)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1218975117.19264.1346370907509.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <95485740.18354.1304426223154.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5213) Write tests to verify the interaction
 of TRUNCATE TABLE and online backup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren updated DERBY-5213:
--------------------------------------

    Attachment: DERBY-5213.diff_2

Thank you for the reviews Rick and Mike.

Rick - you are right of course. For some reason I just didn't want to do a select count, but it's the more logical query, so I changed it.
Mike - I added a comment describing the second fixture, and there was already an assertDirectoryDeleted in org.apache.derbyTesting.junit.BaseTestCase, so I removed the local method.

I'm running regressions now, and assuming they go well, I will commit this patch; then I'll start working on the other testing suggestions.


> Write tests to verify the interaction of TRUNCATE TABLE and online backup
> -------------------------------------------------------------------------
>
>                 Key: DERBY-5213
>                 URL: https://issues.apache.org/jira/browse/DERBY-5213
>             Project: Derby
>          Issue Type: Task
>          Components: SQL, Store
>    Affects Versions: 10.9.1.0
>            Reporter: Rick Hillegas
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY_5213.diff_1, DERBY-5213.diff_2
>
>
> An uncommitted TRUNCATE TABLE command does not block online backup. We should verify that the online and backed up databases are both in a consistent state. At a minimum, we should test the following:
> o uncommitted truncate table followed by online backup and then access the backup copy and access the table.  should see the old data.
> o uncommitred truncate table, followed by online backup that keeps logs,
>   then commit the truncate, and then access the table in the backup.
> For more information, please see this email thread: http://old.nabble.com/truncating-a-table-vs-online-backup-to31524933.html#a31524933

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira