Database Object Deletion Permissions for Safe Restoration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database management systems (DBMS) lack effective methods to prevent accidental deletion of data and restore deleted objects, leading to potential loss of important data.
Innovation Solution
A database service execution method that modifies the operation permission for a to-be-deleted object, prohibiting access and allowing restoration upon request, while managing storage space and object identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the database immediately deletes the object upon deletion request, then the storage space is freed quickly, but the object cannot be restored and data loss occurs
Solution Approach 1:
The patent applies preliminary action by modifying the operation permission of the object to be deleted before actually deleting it. The system prohibits access to the object in advance, allowing the user to potentially restore it if needed, while still preparing for eventual deletion to free storage space.
Solution Approach 2:
The patent implements dynamics by making the deletion process flexible and adjustable. Instead of a static immediate deletion, the system allows dynamic control over the deletion timing through permission modification, enabling the object to remain accessible under certain conditions while being prepared for deletion when storage space is needed.
2Reliability
If the database prohibits access to the to-be-deleted object, then data loss is prevented, but the user cannot access or use the object
Solution Approach 1:
The patent applies dynamics by making access control flexible. The system dynamically adjusts object accessibility based on the deletion status, allowing the object to be inaccessible during deletion preparation but potentially restorable, thus balancing protection with usability.
Solution Approach 2:
The patent implements feedback mechanisms where the system provides information to the user about the deletion status and restoration possibilities. This feedback loop allows users to understand the current state of their objects and take appropriate actions, balancing protection with operational ease.
3Reliability
If the database delays deletion of the object, then the object can be restored, but the storage space is occupied for longer period
Solution Approach 1:
The patent applies preliminary action by preparing the object for deletion in advance through permission modification, while still maintaining the possibility of restoration. This allows the system to be ready for deletion at any time, optimizing the balance between restorability and space occupation.
Solution Approach 2:
The patent implements parameter changes by modifying the operation permission parameter of the object. This parameter change enables the system to control accessibility and timing of deletion, allowing flexible management of storage space while maintaining restoration capability.
Data Source
AI summary
This specification discloses database service execution methods and apparatuses. An object deletion request can be received, and a to-be-deleted object can be determined. However, the to-be-deleted object is not immediately deleted, but an operation permission for the to-be-deleted object is modified, and a user is prohibited from accessing the to-be-deleted object. When an object restoration request that carries an object identifier is received, a to-be-deleted object corresponding to the object identifier is determined from each to-be-deleted object whose operation permission has been modified; and an operation permission for the to-be-deleted object corresponding to the object identifier is modified, and the user is allowed to access the to-be-deleted object corresponding to the object identifier.