US 12,174,822 B2
Processing mutations for a remote database
Jianjun Chen, Cupertino, CA (US); Alfred R. k. Fuller, San Carlos, CA (US); and Steve Tsai, San Jose, CA (US)
Assigned to Google LLC, Mountain View, CA (US)
Filed by Google LLC, Mountain View, CA (US)
Filed on Aug. 23, 2022, as Appl. No. 17/821,635.
Application 17/821,635 is a continuation of application No. 14/928,083, filed on Oct. 30, 2015, granted, now 11,455,291.
Application 14/928,083 is a continuation of application No. 14/748,642, filed on Jun. 24, 2015, granted, now 10,521,417, issued on Dec. 31, 2019.
Claims priority of provisional application 62/016,457, filed on Jun. 24, 2014.
Prior Publication US 2022/0405269 A1, Dec. 22, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 16/00 (2019.01); G06F 16/23 (2019.01); G06F 16/2458 (2019.01); G06F 16/27 (2019.01)
CPC G06F 16/2365 (2019.01) [G06F 16/2329 (2019.01); G06F 16/2358 (2019.01); G06F 16/2474 (2019.01); G06F 16/27 (2019.01)] 18 Claims
OG exemplary drawing
 
1. A computer-implemented method executed by data processing apparatus of a remote version of a database that causes the data processing apparatus to perform operations comprising:
receiving, from a client device, a request requesting to update the remote version of the database with a client version of the database, the remote version of the database comprising a first value for an entity and the client version of the database comprising a second value for the entity that is greater than the first value for the entity, the remote version of the database remote from the client device and the client version of the database stored on the client device, wherein the request comprises:
a client database version number representing a version of the client version of the database; and
a client value to update a corresponding remote value of the remote version of the database;
determining, based on the client database version number of the request and a remote database version number representing the version of the remote version of the database, a conflict;
based on a conflict resolution policy specific to the database, determining that the second value for the entity is greater than the first value for the entity;
based on determining that the second value for the entity is greater than the first value for the entity, determining not to perform the request; and
providing, to the client device, conflict response data indicating that the request was not performed, the conflict response data configured to cause the client device to update the second value for the entity of the client version of the database with the first value for the entity, the conflict response data comprising:
the remote database version number; and
the first value for the entity of the remote version of the database.