View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 160 | Composr | actionlog | public | 2010-04-10 19:41 | 2016-01-21 21:51 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | closed | Resolution | duplicate | ||
| Summary | 160: Undelete | ||||
| Description | Create a new API where you can tell it to monitor deletion queries and upload deletions, putting all deleted data into a buffer. Update the log_it function to stop stop the monitoring session and store it all into a deleted_resources table. [code] undelete_monitor_start(); ... query_delete(...); ... delete_upload(...); ... log_it(...); [/code] Update the action log to be able to undelete these items.Warn that sometimes restoring things can lead to inconsistencies - for example if you restore something that was in a category that was since deleted. Make sure it is possible to undo a restore, and explain this in the interface. Update the deletion messages (e.g. "unreversable and immediate") to note how things can now be undeleted. Create a cleanup tool to purge deleted items. | ||||
| Tags | Risk: Database change | ||||
| Attach Tags | |||||
| Time estimation (hours) | 5 | ||||
| Sponsorship open | |||||
| related to | 162 | Resolved | Chris Graham | Composr documentation | Workflow tutorial |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-08 00:15 | Chris Graham | Tag Renamed | Database change => Risk: Database change |
