Client-side handling of transient duplicates for row-level replication
US9965535B2 · kind B2 · utility
Assignee
Inventors
Key dates
| Filing date | Sep 18, 2012 |
| Grant date | May 8, 2018 |
| Priority date | — |
| Expiry date | Aug 27, 2034 |
Classification
- Technology area (CPC G)Physics
- CPC primaryG06F16/219
- WIPO fieldComputer technology
- WIPO sectorElectrical engineering
Abstract
Transient duplicate key violations of unique key constraints are handled during row updates. Row changes are buffered until a point is reached that those changes are safe to execute. Row changes are effectively reordered to avoid constraint violations during execution of updates. In response to receiving a constraint key violation from a server after an attempted update, a client locally stores a record containing information regarding the failed update. Later, in response to the lack of receipt of an error in response to another update to the same column of the same table, the client uses the information in this record to instruct the server to attempt to repeat a failed update that previously attempted to change the value of a row to a value that was present in a uniqueness-constrained column at the time of the failure, but is no longer present due to the successful update.
Source: USPTO / EPO open patent data. Objective bibliographic and citation counts.