Transaction-based refresh of a long database transaction's workspace
Inventors
Assignees
Interested in licensing this patent?
MTEC can help explore whether this patent might be available for licensing for your application.
Abstract
Aspects of the present disclosure aim to improve upon systems for managing long database transactions, and the way in which changes made to a database from within a workspace view during a long transaction are committed to the underlying parent database. The present disclosure aims to solve problems caused by the need to refresh a workspace view as part of the process of resolving conflicts between competing workspace views operating on the same portions of the database. Aspects described herein solve the problem through the creation of a separate data structure which effectively logs all of the further transactions which commit changes to parent database. The data structure can be arranged to include all changes committed after a first transaction is opened and worked upon. The process of committing the changes made in the first transaction to the workspace includes performing a recursive search using the data structure.
Core Innovation
The invention relates to managing long database transactions so that a transaction workspace view is refreshed within a live workspace of a parent database while a first transaction remains open. A separate data structure records changes from one or more further transactions committed to the parent database while the first transaction is open, and the transaction workspace view is opened in response to the first transaction being opened within the live workspace at a first time.
When the first change is later committed at a second time, the committing process recursively searches the separate data structure to identify further transactions that have acted on the first record. For any further records acted upon by the further transactions, the process identifies any still further transactions having acted upon the further records until no further transactions are found, and the transaction workspace view of the first transaction is refreshed with changes to the records acted upon by the further transactions identified in the recursive search.
Based on the refreshed transaction workspace view, the system resolves conflicts between the first change and the changes to the records acted upon by the further transactions, and committing is performed in dependence on any resolved conflicts. In preferred implementations described in the dependent claims, recursion is performed by traversing a graph of earlier completed transactions with edges indicating at least one shared record, and refreshing orders changes to maintain data referential integrity.
Claims Coverage
The independent claims are directed to recursive conflict-aware refreshing of a transaction workspace view using a separate transaction-change logging structure, a networked computer system implementing the workflow, and managing long database transactions for refreshing as part of resolving conflicts between competing workspace views. Across the independent claims, inventive features include opening a transaction workspace view in response to a first transaction opening, creating a separate data structure that includes changes from further committed transactions, recursively searching that data structure to identify dependent transactions and records, refreshing the transaction workspace view with the recursively identified changes, resolving conflicts based on the refreshed view, and committing in dependence on resolved conflicts.
Recursive conflict-aware refreshing of a transaction workspace view
Recursively searching the data structure to identify further transactions having acted on the first record, recursively identifying still further transactions for further records acted upon, refreshing the transaction workspace view of the first transaction with the changes to the records acted upon by the further transactions identified in the recursive search, and resolving conflicts between the first change and the changes based on the refreshed transaction workspace view before committing in dependence on any resolved conflicts.
Separate data structure logging changes from further transactions while a transaction is open
Creating a data structure arranged to include any changes from one or more further transactions which are committed to the parent database while the first transaction is open.
Opening a transaction workspace view in a live workspace of a parent database responsive to a first transaction
Opening a transaction workspace view within a live workspace of a parent database at a first time in response to a first transaction being opened.
Recursive search by graph traversal with shared record semantics
Performing the recursive search by traversing a graph whose nodes represent earlier completed transactions included in the first transaction, and whose edges indicate that at least one shared record exists between the transactions connected by the edge.
Refreshing with changes ordered to maintain referential integrity
Refreshing the workspace view involves ordering changes from subsequent transactions to maintain data referential integrity of the data.
Managing long database transaction for refreshing while resolving conflicts between competing workspace views
Managing a long database transaction to permit refreshing of a workspace view within a live workspace as part of resolving conflicts between competing workspace views operating on same portions of the database, including creating a separate data structure that logs transactions which commit changes after a first transaction is opened and refreshing the first workspace view with changes to portions acted upon by further transactions identified by a recursive search.
The claims center on using a separate transaction-change logging data structure to support recursive identification of further transactions affecting records or portions during long transactions, refreshing the first transaction workspace view with the recursively identified changes, resolving conflicts based on the refreshed view, and committing in dependence on resolved conflicts, with refinements including graph traversal and referential integrity ordering.
Stated Advantages
Enables committing the first change in dependence on resolved conflicts by refreshing the transaction workspace view with changes from further transactions identified via recursive searching.
Permits refreshing of a workspace view within a live workspace of a database as part of resolving conflicts between competing workspace views operating on same portions of the database.
Supports recursive identification of further transactions and their acted-upon records or portions until no further transactions are found, so the refreshed view reflects relevant committed changes.
Documented Applications
Managing long database transaction handling for transaction and workspace timeline scenarios in a live workspace, including resolving conflicts between competing workspace views operating on same portions of the database.
Use in datasets involving spatial features, including polygon geometry, with refreshed-geometry outcomes when integrating transaction changes and resolving conflicts.
Interested in licensing this patent?