Please download the dossier by clicking on the dossier button x
×

Update manager for database system

  • US 7,734,648 B2
  • Filed: 04/11/2006
  • Issued: 06/08/2010
  • Est. Priority Date: 04/11/2006
  • Status: Active Grant
First Claim
Patent Images

1. A data management method, comprising:

  • in response to a first read request to read data from a group of databases;

    reading a requested data object referenced by the first read request from a database of the group of databases, andreturning the requested data object and a first update token to a sender of the first read request, wherein the first update token is generated by applying a hash function to selected data fields of the requested data object for which data inconsistencies cannot be tolerated and the first update token is not changed before any data in the selected data fields of the requested data object is changed, other data fields not selected are omitted by the hash function and the other data fields not selected are data fields for which data inconsistencies can be tolerated; and

    in response to a second read request to read the requested data object from the database;

    returning the requested data object and the first update token to a sender of the second read request,in response to a first write request to store updated data for the requested data object to the database;

    storing updated data for the requested data object to the database, the updated data comprise updates to at least one selected data fields for which data inconsistencies cannot be tolerated;

    generating a second update token by applying the hash function to the selected data fields of the requested data object for which data inconsistencies cannot be tolerated;

    in response to a second write request to store updated data for the requested data object to the database;

    comparing the second update token to an update token contained in the second write request to store updated data, andwhen the second update token and the update token contained in the second write request to store updated data match, storing data received in the second write request to the database,wherein the second update token and the update token contained in the second write request to store updated data will match even if updates to the requested data object stored at the database have occurred during a time between generation of the update token contained in the second write request to store updated data and the second update token, provided the updates to the stored requested data object are only directed to data fields thereof that are tolerant of data inconsistencies, andwherein the group of databases comprise a first database that provides native support for update control that prevents inconsistencies introduced by multiple attempts to update same data simultaneously and a second database that does not provide native support for update control that prevents inconsistencies introduced by multiple attempts to update same data simultaneously.

View all claims
  • 2 Assignments
Timeline View
Assignment View
    ×
    ×