db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-5213) Write tests to verify the interaction of TRUNCATE TABLE and online backup
Date Fri, 14 Jun 2013 17:28:20 GMT

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

Rick Hillegas closed DERBY-5213.
--------------------------------

    
> 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
>             Fix For: 10.10.1.1
>
>         Attachments: DERBY_5213.diff_1, DERBY-5213.diff_2, DERBY-5213.diff_3
>
>
> 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

Mime
View raw message