You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2012/08/29 03:09:07 UTC
[jira] [Commented] (DERBY-5213) Write tests to verify the
interaction of TRUNCATE TABLE and online backup
[ https://issues.apache.org/jira/browse/DERBY-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443714#comment-13443714 ]
Myrna van Lunteren commented on DERBY-5213:
-------------------------------------------
oops, just realized I forgot to undo the changes to lang._Suite in my initial patch for this - I commented out a bunch of tests for a mini-trial run.
That's of course not intended for commit.
> 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
>
>
> 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