Patent US5671407A successfully refreshed from Google Patents.
← Back to Patent Explorer
US5671407A Expired / Lapsed US ⏱️ 0.0 years remaining

Application-specific conflict detection for weakly consistent replicated databases

Assignee: Gula Consulting LLC
•
Filing: 1994-12-07
•
Granted: 1997-09-23
•
Expires: 2014-12-07
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract Write operations for weakly consistent replicated database systems have application-specific embedded dependency queries and related descriptions of the results that are expected to be returned when the respective dependency queries are run against the database. The dependency queries are arbitrary queries that are provided by the application to satisfy the requirements of the application. Write operations that conflict with the current state of any given instance of such a database are detected by comparing (a) the results that are returned when the dependency queries for those writes are run against the given instance of the database with (b) the results that are expected to be returned.

Inventors

  • 👤 Alan J. Demers
  • 👤 Karin Petersen
  • 👤 Michael J. Spreitzer
  • 👤 Douglas B. Terry
  • 👤 Marvin M. Theimer
  • 👤 Brent B. Welch

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-11-04 13:46
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/20; G06F16/23; G06F16/2308; G06F16/2315; G06F16/2329; G06F16/2379; Y; Y10; Y10S; Y10S707/00; Y10S707/99931; Y10S707/99938; Y10S707/99951; Y10S707/99952; Y10S707/99953

Claims Analysis

Total Claims: 2
Claim 1
Independent Claim 209 words
An application-specific process for detecting write operations which conflict with whatever state a database is found to have whenever any of said write operations is presented for updating said database; said process comprising embedding at least one dependency query in each of said write operations, together with a corresponding description of any results which are expected to be produced when said query is run against said database, where said dependency query is an arbitrary query on the database that is provided by the application as required to satisfy requirements of the application; running each of the embedded dependency queries for any given write operation against said database whenever said given write operation is presented for updating said database until a conflict is detected or all of said queries have been applied; collecting all results produced when any given dependency query for said given write operation is run against said database; comparing the results produced by running said given dependency query against said database with the expected results of so doing; and identifying a given write operation as being in conflict with the state of said database whenever the results produced by running any given one of the dependency queries for the given write fail to match the expected results.
Claim 2
Dependent Claim 209 words
An application-specific process for detecting write operations which conflict with whatever state a database is found to have whenever any of said write operations is presented for updating said database; said process comprising embedding at least one dependency query in each of said write operations, together with a corresponding description of any results which are expected to be produced when said query is run against said database, where said dependency query is an arbitrary query on the database that is provided by the application as required to satisfy requirements of the application; running each of the embedded dependency queries for any given write operation against said database whenever said given write operation is presented for updating said database until a conflict is detected or all of said queries have been applied; collecting all results produced when any given dependency query for said given write operation is run against said database; comparing the results produced by running said given dependency query against said database with the expected results of so doing; and identifying a given write operation as being in conflict with the state of said database whenever the results produced by running any given one of the dependency queries for the given write fail to match the expected results.

References Cited (Backward Citations)

US5255387A Cited
US5287496A Cited
US5280612A Cited
US5551027A Cited
US5588147A Cited
US5581753A Cited
US5577240A Cited
US5581754A Cited
US5603026A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2000-09-22 2001-03-24 2001-09-23 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2004-09-22 2005-03-24 2005-09-23 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2008-09-22 2009-03-24 2009-09-23 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag