Allowing inconsistency in a distributed client-server application

• US 5,751,958 A
• Filed: 06/30/1995
• Issued: 05/12/1998
• Est. Priority Date: 06/30/1995
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Peoplesoft (Oracle Corporation)
• Inventors: Vershel, Mark A., Pettus, Christophe E., Zweben, Monte, Deale, Michael J.
• Primary Examiner(s): Donaghue, Larry D.
• Application Number:
  US08/497,506
• Time in Patent Office: 1,047 Days
• Field of Search: 395/200.03, 395/200.04, 395/200.09, 395/608, 395/610, 395/617, 395/619, 395/200.34, 395/200.31, 395/703, 707/8
• US Class Current: 709/204
• CPC Class Codes: G06F 16/2329 using versioning
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database

Abstract

The invention enables multiple users to simultaneously access and change the contents of a database in a flexible manner. Each user interacts with a working copy of a master copy of the database. The contents of each of the working copies of the database can be accessed and manipulated so that the contents of the working copy of the database can be revised. Each user has control over whether to the "publish" revisions made to the contents of that user'"'"'s working copy of the database, i.e., write the revisions to the master copy and present other users with the option of including the revisions in the working copies of those other users. Each user has the option to reject revisions published by other users so that the contents of each user'"'"'s working copy of the database may or may not be maintained consistent with other working copies of the database operated on by other users. However, in order to ensure data integrity of the master database, each user that rejects the inclusion of revisions published by another user is prospectively prevented from publishing revisions to other users, until the user accepts the previously rejected published revisions. The invention employs a distributed architecture that allows each user to interact with that user'"'"'s working copy of the database in a way that is controlled by that user without impairing the functionality of the database for other users. The database inconsistency allowed by the invention facilitates the performance by users of "what-if" analyses.

Claims

1. A system for enabling multiple users to simultaneously access and change the contents of a database, comprising:

means for storing a master copy of the database;

means for storing a plurality of working copies of one or more datasets of the database;

means for allowing a corresponding one of the users to access and manipulate the contents of each of two or more of the working copies so that the contents of the two or more working copies can be revised;

means for enabling at least one user of the two or more working copies to publish revisions made to a working copy by the at least one user;

means for updating the contents of the master copy of the database with the published revisions;

means for presenting to each user of a working copy of a dataset that is affected by the revisions the option to accept or reject the inclusion of the revisions in that working copy;

means for updating the working copy of each dataset with accepted published revisions that affect that dataset; and

means for preventing each user that has rejected the inclusion of revisions in the user'"'"'s working copy of a dataset from publishing revisions.

2. A system as in claim 1, wherein:

the means for storing a master copy further comprises a persistent data storage means;

the means for storing a plurality of working copies further comprises a plurality of non-persistent, rapidly accessible memory means;

the means for allowing further comprises a plurality of combinations of one or more client computers and a server computer;

the means for enabling further comprises a publishing computer;

means for updating the master copy further comprises a publishing computer;

means for presenting further comprises a plurality of combinations of one or more client computers and a server computer;

means for updating the working copy further comprises a publishing computer and a server computer; and

the means for preventing further comprises a publishing computer.

4. A system as in claim 1, further comprising:

means for storing, for each working copy of a dataset for which at least one set of published revisions has been rejected, a set of cumulative revisions representing the cumulative changes made to the working copy of the dataset by the set or sets of published revisions that have been rejected; and

means for updating such a working copy of a dataset with the corresponding set of cumulative revisions whenever current published revisions affecting the working copy of the dataset are accepted.

5. A system as in claim 1, wherein:

the means for storing a master copy further comprises a persistent data storage means; and

the means for storing a plurality of working copies further comprises a plurality of non-persistent, rapidly accessible memory means.

6. A system as in claim 1, wherein:

the means for storing a master copy further comprises a persistent data storage means; and

the means for storing a plurality of working copies further comprises a persistent data storage means.

7. A system as in claim 1, wherein the database is an object-oriented database.

8. A system as in claim 1, wherein the database is a relational database.

9. A system as in claim 1, further comprising means for enabling a user that has previously rejected revisions to the working copy of a dataset being used by that user to accept one or more previously rejected revisions.

3. A method for enabling multiple users to simultaneously access and change the contents of a database, comprising:

storing a master copy of the database;

storing a plurality of working copies of one or more datasets of the database;

allowing a corresponding one of the users to access and manipulate the contents of each of two or more of the working copies so that the contents of the two or more working copies can be revised;

enabling at least one user of the two or more working copies to publish revisions made to a working copy by the at least one user;

updating the contents of the master copy of the database with the published revisions;

presenting to each user of a working copy of a dataset that is affected by the revisions the option to accept or reject the inclusion of the revisions in that working copy;

updating the working copy of each dataset with accepted published revisions that affect that dataset; and

preventing each user that has rejected the inclusion of revisions in the user'"'"'s working copy of a dataset from publishing revisions.

10. A system for mediating use of a database by a plurality of users, comprising:

means for enabling each of the users to obtain a working copy of a dataset, each dataset including some portion or all of the data in the database;

means for enabling a user to revise the data in a working copy of a dataset obtained by that user;

means for enabling a user to publish a set of revisions made to a working copy of a dataset;

means for determining, for each working copy of a dataset affected by a current set of published revisions, whether to accept or reject incorporation of the current set of published revisions into the affected working copy of the dataset;

means for updating an affected working copy of a dataset with a set of accepted published revisions; and

means for preventing publication of a set of revisions from, or acceptance of a set of published revisions by, each working copy of a dataset for which a previous set of published revisions was rejected.

11. A system as in claim 10, wherein:

the means for enabling a user to revise further comprises means for storing net changes in the data values of the working copy of a dataset obtained by that user, the net changes representing a difference between an initial set of data values and an ending set of data values, wherein;

the initial set of data values of a working copy of a dataset are the data values either immediately after the working copy of the dataset has been obtained by the user or immediately after the user has published revisions made to the working copy of the dataset;

the ending set of data values of a working copy of a dataset are the data values immediately before the user publishes revisions made to the working copy of the dataset; and

each set of published revisions comprises the net changes between the most recent initial and ending sets of data values for the working copy of the dataset; and

the means for updating further comprises means for adding the net changes corresponding to a published set of revisions to the data values of each working copy of a dataset for which the published revisions are accepted.

12. A system as in claim 11, wherein the means for enabling a user to revise further comprises means for storing, in addition to the net changes, one of the initial set of data values or ending set of data values.

13. A system as in claim 11, further comprising:

means for associating each set of net changes with each working copy of a dataset for which the net changes were rejected;

means for enabling a user of a working copy of a dataset for which a set of net changes were rejected to accept a set of rejected net changes that affect that working copy of a dataset; and

means for updating that working copy of a dataset with one or more sets of previously rejected net changes.

14. A system as in claim 10, further comprising:

means for associating each set of published revisions with each working copy of a dataset for which the published revisions were rejected;

means for enabling a user of a working copy of a dataset for which a set of published revisions were rejected to accept a set of rejected published revisions that affect that working copy of a dataset; and

means for updating that working copy of a dataset with one or more sets of previously rejected published revisions.

15. A method for mediating use of a database by a plurality of users, comprising the steps of:

enabling each of the users to obtain a working copy of a dataset, each dataset including some portion or all of the data in the database;

enabling a user to revise the data in a working copy of a dataset obtained by that user;

enabling a user to publish a set of revisions made to a working copy of a dataset;

determining, for each working copy of a dataset affected by a current set of published revisions, whether to accept or reject incorporation of the current set of published revisions into the affected working copy of the dataset;

updating an affected working copy of a dataset with a set of accepted published revisions; and

preventing publication of a set of revisions from, or acceptance of a set of published revisions by, each working copy of a dataset for which a previous set of published revisions was rejected.

16. A method as in claim 15, further comprising the step of updating the database with each set of published revisions.

17. A method as in claim 15, wherein:

the step of enabling a user to revise further comprises the step of storing net changes in the data values of the working copy of a dataset obtained by that user, the net changes representing a difference between an initial set of data values and an ending set of data values, wherein;

the initial set of data values of a working copy of a dataset are the data values either immediately after the working copy of the dataset has been obtained by the user or immediately after the user has published revisions made to the working copy of the dataset;

the ending set of data values of a working copy of a dataset are the data values immediately before the user publishes revisions made to the working copy of the dataset; and

each set of published revisions comprises the net changes between the most recent initial and ending sets of data values for the working copy of the dataset; and

the step of updating further comprises the step of adding the net changes corresponding to a published set of revisions to the data values of each working copy of a dataset for which the published revisions are accepted.

18. A method as in claim 17, wherein the step of enabling a user to revise further comprises the step of storing, in addition to the net changes, one of the initial set of data values or ending set of data values.

19. A method as in claim 17, further comprising, after the step of determining, the steps of:

associating each set of net changes with each working copy of a dataset for which the net changes were rejected;

enabling a user of a working copy of a dataset for which a set of net changes were rejected to accept a set of rejected net changes that affect that working copy of a dataset; and

updating that working copy of a dataset with one or more sets of previously rejected net changes.

20. A method as in claim 15, further comprising, after the step of determining, the steps of:

associating each set of published revisions with each working copy of a dataset for which the published revisions were rejected;

enabling a user of a working copy of a dataset for which a set of published revisions were rejected to accept a set of rejected published revisions that affect that working copy of a dataset; and

updating that working copy of a dataset with one or more sets of previously rejected published revisions.