[
https://issues.apache.org/jira/browse/DERBY-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-5213:
--------------------------------------
Attachment: DERBY_5213.diff_1
Attaching a patch which does mostly precisely what was suggested in the email
exchange, and this patch is ready for review.
I think there are some further tests that can be added, for instance, there's
some discussion in the reference guide about using blocking or not blocking
behavior of SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE and
SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_NOWAIT.
Perhaps also a test that tries to do a rollback of the truncate table.
> 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
