Multitenant Database Object Deletion via Deprecation Patching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multitenant database systems, the inability to delete delivered objects leads to unnecessary data, hindering efficient management and implementation due to data preservation mechanisms that prevent object deletion to avoid data loss.
Innovation Solution
A two-step patch process is implemented, where the first patch marks objects for deprecation and prevents further usage, followed by a second patch that allows deletion of the objects, ensuring data integrity and enabling removal of unused objects while preventing unintended data loss.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If deletion of delivered objects is prevented to ensure data preservation and system-wide support, then data integrity is maintained, but system overhead increases and application performance deteriorates due to accumulation of unnecessary objects
Solution Approach 1:
The patent segments the object deletion process into two distinct phases: (1) a first patch that marks objects for deprecation and prevents new usage, and (2) a second patch that enables deletion of marked objects. This segmentation allows the system to maintain data integrity for actively used objects while enabling cleanup of deprecated objects, thus resolving the contradiction between data preservation and performance optimization
Solution Approach 2:
The patent applies preliminary action by first marking objects for deprecation before allowing their deletion. The first patch preemptively identifies and marks objects that are no longer needed, creating a controlled set of candidates for deletion. This preliminary marking ensures that only appropriately selected objects are deleted, maintaining data integrity while enabling performance improvement through removal of unnecessary objects
2Reliability
If delivered objects are retained in the system, then data loss is prevented, but system complexity increases due to accumulation of unused objects across multiple tenants
Solution Approach 1:
The patent extracts deprecated objects from the active system through a two-step process. The first patch identifies and marks objects for deprecation, effectively separating them from actively used objects. The second patch then enables deletion of these extracted marked objects. This extraction approach allows the system to maintain data preservation for needed objects while reducing system complexity by removing unused objects
Solution Approach 2:
The patent changes the status parameter of objects from 'active' to 'deprecated' through the first patch, which modifies system behavior regarding these objects. This parameter change enables differential treatment: deprecated objects can be deleted while active objects remain protected. The second patch further changes the deletion permission parameter, allowing removal of deprecated objects. These parameter changes resolve the contradiction by creating a distinction between preservable and removable objects
3Ease of operation
If a two-step patch process is implemented to enable object deletion, then developer management efficiency improves, but implementation complexity increases
Solution Approach 1:
The patent segments the object deletion capability into two distinct patches with clearly defined responsibilities. The first patch handles object identification and marking, while the second patch handles deletion enablement. This segmentation improves developer management efficiency by providing a controlled, step-by-step process that prevents accidental deletion of active objects. The clear separation of concerns makes the implementation complexity manageable and the process easier to understand and maintain
Data Source
AI summary
Data characterizing an object for deprecation and code characterizing a modification to an application is received at a code development system. The object is for deprecation and the application is deployed on a plurality of tenants of a production database management system. A first application patch is generated according to the received code. The first patch includes computer executable instructions that during deployment to a target system configure the target system to prevent further usage by tenants of the object for deprecation. The first application patch is deployed to the plurality of tenants. A second application patch is generated. The second application patch includes computer executable instructions that during deployment to the target system configure the target system to allow deletion of the object from the target system. The second application patch is deployed to the plurality of tenants. Related apparatus, systems, techniques, and articles are also described.