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/09/07 20:35:07 UTC

[jira] [Comment Edited] (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=13450867#comment-13450867 ] 

Myrna van Lunteren edited comment on DERBY-5213 at 9/8/12 5:33 AM:
-------------------------------------------------------------------

Thanks for noticing those failures Knut. 
I'll take a look at it on Monday. I've disabled the test (commented out in lang._Suite) for now with revision: http://svn.apache.org/viewvc?view=revision&revision=1382114.
                
      was (Author: myrna):
    Thanks for noticing those failures Knut. 
I'll take a look at it on Monday. I've disabled (commented out in lang._Suite) for now with revision: http://svn.apache.org/viewvc?view=revision&revision=1382114.
                  
> 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