Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 3 May 2011 12:37:03 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <95485740.18354.1304426223154.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (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

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.0.0
            Reporter: Rick Hillegas


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.
For more information on JIRA, see: http://www.atlassian.com/software/jira