Dynamic retention policies and optional deletes
US-2019347046-A1 · Nov 14, 2019 · US
US10860606B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10860606-B2 |
| Application number | US-201815884944-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 31, 2018 |
| Priority date | Jan 31, 2018 |
| Publication date | Dec 8, 2020 |
| Grant date | Dec 8, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed are examples of systems, apparatus, methods and computer program products for deleting data of an object within a multi-tenant database. Described is a mechanism for performing operations such as an efficient delete operation by introducing a new delete operation (or method) that is configured to allow a data structure such as an object to identify one or more records to be deleted. In order to ensure that the operation is efficient, the mechanism may perform a validation of the values provided to the delete operation based on the type of data store used for storing the records. For example, the validation may ensure that the values provided to the method correspond to a composite primary key when records are stored in a non-relational data store. Upon a successful validation, an initial delete request may be translated to an appropriate delete operation for the underlying database.
Opening claim text (preview).
What is claimed is: 1. A system comprising: one or more processors; and a non-transitory computer readable medium storing a plurality of instructions, which when executed, cause the one or more processors to perform operations comprising: receiving a first request to delete data related to a first data object of a plurality of data objects associated with a first organization in a multi-tenant database system, the first request identifying a data structure that specifies values for one or more fields of the first data object; validating that the specified values for the one or more fields satisfy one or more performance requirements for identifying one or more records of the first data object; translating the first request to delete data to a database delete operation, the database delete operation using the specified values to identify one or more records of the first organization to be deleted; and initiating a synchronous delete of the identified one or more records of the first organization by executing the database delete operation. 2. The system of claim 1 , the operations further comprising: validating, using metadata associated with the first data object, that the specified values for the one or more fields correspond to at least a portion of a composite primary key defined for the first data object. 3. The system of claim 1 , the operations further comprising: determining the data related to the first data object is stored in a non-relational data store. 4. The system of claim 1 , the operations further comprising: validating, using one or more permissions associated with the data object, that the first organization is authorized to access the data object. 5. The system of claim 1 , wherein the first request invokes a delete operation of an application platform of the multi-tenant database system and the data structure comprises an object passed as an argument to the delete operation. 6. The system of claim 1 , wherein the data structure includes only values for an entirety of the composite primary key. 7. The system of claim 1 , wherein the specified values corresponding to the composite primary key for the first data object substitute for one or more unique row identifiers for the one or more records of the first organization to be deleted when executing the database delete operation. 8. The system of claim 1 , the operation further comprising: receiving a second request to delete data related to a second data object of a plurality of data objects associated with a second organization in the multi-tenant database system, the second request identifying a data structure that specifies values for one or more fields of the second data object; validating that the specified values correspond to one or more unique row identifiers for one or more records of the second data object; and initiating a synchronous delete of the one or more records of the second organization. 9. The system of claim 1 , wherein the validating is performed on an API layer of an application platform of the multi-tenant database system and the database delete operation is performed by the database and initiated by the application platform. 10. The system of claim 1 , wherein the first request to delete data is received via a REST API, SOAP API, or an application platform specific programming language. 11. A method comprising: receiving, by a multi-tenant database system, a first request to delete data related to a first data object of a plurality of data objects associated with a first organization in the multi-tenant database system, the first request identifying a data structure that specifies values for one or more fields of the first data object; validating that the specified values for the one or more fields satisfy one or more performance requirements for identifying one or more records of the first data object; translating, by the multi-tenant database system, the first request to delete data to a database delete operation, the database delete operation using the specified values to identify one or more records of the first organization to be deleted; and initiating a synchronous delete of the identified one or more records of the first organization by executing the database delete operation. 12. The method of claim 11 , further comprising: determining the data related to the data object is stored in a non-relational data store. 13. The method of claim 11 , further comprising: validating, using metadata associated with the first data object, that the specified values for the one or more fields correspond to at least a portion of a composite primary key defined for the first data object. 14. The method of claim 11 , wherein the first request invokes a delete operation of an application platform of the multi-tenant database system and the data structure comprises an object passed as an argument to the delete operation. 15. The method of claim 11 , further comprising: receiving a second request to delete data related to a second data object of a plurality of data objects associated with a second organization in the multi-tenant database system, the second request identifying a data structure that specifies values for one or more fields of the second data object; validating that the specified values correspond to one or more unique row identifiers for one or more records of the second data object; and initiating a synchronous delete of the one or more records of the second organization. 16. The method of claim 11 , wherein the specified values corresponding to the composite primary key for the data object substitute for one or more unique row identifiers for the one or more records of the first organization to be deleted when executing the database delete operation. 17. A computer program product comprising computer-readable program code capable of being executed by one or more processors when retrieved from a non-transitory computer-readable medium, the program code including instructions to: receive a first request to delete data related to a first data object of a plurality of data objects associated with a first organization in a multi-tenant database system, the request identifying a data structure that specifies values for one or more fields of the first data object; validate that the specified values for the one or more fields satisfy one or more performance requirements for identifying one or more records of the first data object; translate the request to delete data to a database delete operation, the database delete operation using the specified values to identify one or more records of the first organization to be deleted; and initiate a synchronous delete of the identified one or more records of the first organization by executing the database delete operation. 18. The computer program product of claim 17 , the program code comprising further instructions to: determine the data related to the data object is stored in a non-relational data store. 19. The computer program product of claim 17 , the program code comprising further instructions to: validate, using metadata associated with the first data object, that the one or more fields of the specified values correspond to at least a portion of a composite primary key defined for the data object. 20. The computer program product of claim 17 , the program code comprising further instructions to: receive a second request to delete data related to a second data object of a plurality of data objects associated with a second organization in the
Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket · CPC title
with details for schema evolution support · CPC title
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
by facilitating the interaction with a user or administrator · CPC title
Delete operations (erasing in storage systems G06F3/0652) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.