Method of monitoring changes in attribute values of object in an object-oriented database

• US 5,133,075 A
• Filed: 12/19/1988
• Issued: 07/21/1992
• Est. Priority Date: 12/19/1988
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Company (HP Inc.)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Risch, Tore J. M.
• Primary Examiner(s): Lee, Thomas C.
• Assistant Examiner(s): Geckil, Mehmet
• Application Number:
  US07/286,556
• Time in Patent Office: 1,310 Days
• Field of Search: 364/200 MS File, 364/401, 364/900 MS File, 395/800, 395/725, 395/600
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A method of monitoring objects in an interactive object-oriented database system. Any of a plurality of client programs can request monitoring of attributes of objects in the database. A record is kept of update transactions initiated by a client. When the client commits the changes, any client which has requested monitoring is notified of any change in the value of an attribute being monitored at the request of that client. The notification interrupts the client and invokes a predesignated client procedure. Overhead is minimized by creating partial view materialization paths and defining monitors ahead of time and by localizing the monitoring.

Claims

1. In a computer database system, a method of monitoring an object in a database in response to a request from any of a plurality of client programs, the method comprising the following steps carried out by the system:

keeping a record of any request from a client to monitor an attribute of the object, the attribute depending on another attribute;

keeping a record indicating interdependence relationships among the attributes;

keeping a record of the value of each attribute being monitored by accessing said interdependence relationship record;

during a database update session, keeping a record of any database update transactions initiated by a client; and

if a client which has initiated an update transaction requests that said update transaction be stored in the database;

determining which monitored attributes may have been affected by said transaction;

determining whether the values of any of said attributes have changed by computing updated values form said attributes and comparing the updated values with the values in the attribute value record; and

for each value which has changed, notifying any client which had requested monitoring of that attribute.

2. A method according to claim 1 wherein notifying a client comprises interrupting any task then being performed by the client and invoking a predesignated client procedure.

3. A method according to claim 1 wherein notifying a client comprises:

if the client is in an interruptible state, interrupting any task then being performed by the client and invoking a predesignated client procedure; and

if the client is not in an interruptible state;

keeping a record of the notification until the client enters an interruptible state; and

when the client enters an interruptible state, interrupting any task then being performed by the client and invoking a predesignated client procedure.

4. A method according to claim 1 wherein notifying a client comprises:

if the client is in an interruptible state, interrupting any task then being performed by the client and invoking a predesignated client procedure; and

if the client is not in an interruptible state, keeping a record of the notification until the client requests notification and then invoking said predesignated client procedure.

5. A method according to claim 1 and further comprising optimizing a partial view materialization path for a given attribute in advance of any request to monitor that attribute.

6. A method according to claim 1 and further comprising defining a monitor procedure for a given attribute in advance of any request to monitor that attribute.

7. A method according to claim 6 wherein defining a monitor procedure comprises creating means for keeping the record of any request from a client.

8. A method according to claim 6 wherein defining a monitor procedure comprises creating means for keeping a record of the value of the attribute being monitored.

9. A method according to claim 1 and further comprising clearing the record of update transactions after determining whether any attribute values have changed.

10. In a computer database system, a method of monitoring an object in a database in response to a request from any of a plurality of client programs, the method comprising the following steps carried out by the system;

keeping a record of any request from a client to monitor an attribute of the object, the attribute depending on another attribute;

keeping a record indicating interdependence relationships among the attributes;

keeping a record of the value of each attribute being monitored by accessing said interdependence relationship record;

during a database update session, keeping a record of any database update transactions initiated by a client; and

if a client request notification of any changes which have occurred in an attribute then being monitored for that client;

determining which monitored attributes may have been affected during said database update session;

determining whether the values of any of said attributes have changed by computing updated values for said attributes an comparing the updated values with the values in the attribute value record; and

notifying the client which requested notification of each value which has changed.

11. A method according to claim 10 and further comprising keeping a record of the changes for later notification of any other clients for which attributes are then being monitored.

12. A method according to claim 10 wherein notifying the client which requested notification comprises interrupting any task then being performed by the client and invoking a predesignated client procedure.

13. A method according to claim 10 and further comprising optimizing a partial view materialization path for a given attribute in advance of any request to monitor that attribute.

14. A method according to claim 10 and further comprising defining a monitor procedure for a given attribute in advance of any request to monitor that attribute.

15. A method according to claim 14 wherein defining a monitor procedure comprises creating means for keeping the record of any request from a client.

16. A method according to claim 14 wherein defining a monitor procedure comprises creating means for keeping a record of the value of the attribute being monitored.

17. A method according to claim 10 and further comprising clearing the record of update transactions after determining whether any attribute values have changed.

18. In a computer database system, a method of monitoring an object in a database in response to a request from any of a plurality of client programs, the method comprising the following steps carried out by the system;

keeping a record of any request form a client to monitor an attribute of the object, the attribute depending on another attribute;

keeping a record indicating interdependence relationships among the attributes;

keeping a record of the value of each attribute being monitored by accessing said interdependence relationship record;

during a database update session, keeping a record of any database update transactions initiated by a client;

if a client which has initiated an update transaction request that said update transaction be stored in the database;

determining which monitored attributes may have been affected by said update transaction;

determining whether the values of any of said attributes have changed by computing updated values for said attributes and comparing the updated values with the values in the attribute value record; and

for each value which has changed, notifying any client which requested monitoring of that attribute; and

if a client request notification of any changes which have occurred in an attribute then being monitored for that client;

determining which monitored attributes may have been affected during said database update session;

determining whether the values of any of said attributes have changed by computing updated values for said attributes and comparing the updated values with the values in the attribute value record; and

notifying the client which requested notification of each value which has changed.

19. A method according to claim 18 wherein the last step further comprises keeping a record of the changes for later notification of any other clients for which attributes are then being monitored.

20. A method according to claim 18 wherein notifying a client comprises interrupting any task then being performed by the client and invoking a predesignated client procedure.

21. A method according to claim 18 and further comprising clearing the record of update transactions after determining whether any attribute values have changed.