db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5213) Write tests to verify the interaction of TRUNCATE TABLE and online backup
Date Tue, 11 Sep 2012 23:46:07 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453559#comment-13453559
] 

Myrna van Lunteren commented on DERBY-5213:
-------------------------------------------

I've taken a quick look, and it seems to me the problem was that the sequence of the tests
*was* important - one of the tests did a truncate table and committed it.
As that wasn't my intention, I've removed the decorateSQL and put the relevant code into the
setUp() and dropped the table in a teardown() method.
                
> 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

Mime
View raw message