US 7,321,898 B1 | ||
Locking mechanism for materialized views in a database system | ||
Gang Luo, Madison, Wis. (US); Michael W. Watzke, Madison, Wis. (US); Curt J. Ellmann, Madison, Wis. (US); and Jeffrey F. Naughton, Madison, Wis. (US) | ||
Assigned to NCR Corp., Dayton, Ohio (US) | ||
Filed on May 13, 2004, as Appl. No. 10/844,680. | ||
Application 10/844680 is a continuation in part of application No. 10/349855, filed on Jan. 23, 2003, granted, now 7,174,331. | ||
Application 10/349855 is a continuation in part of application No. 10/324456, filed on Dec. 20, 2002, granted, now 7,181,452. | ||
Application 10/324456 is a continuation in part of application No. 10/117497, filed on Apr. 04, 2002, granted, now 7,149,737. | ||
Int. Cl. G06F 7/00 (2006.01) |
U.S. Cl. 707—102 | 24 Claims |
1. A method for use in a database system, comprising:
receiving a transaction that causes a tuple to be integrated into a join view;
in response to receiving the transaction, placing a predefined first lock on at least a portion of the join view, the predefined
first lock conflicting with either a shared lock or an exclusive lock placed on the join view, but not conflicting with another
predefined first lock placed on the join view; and
obtaining a latch associated with a value of a predetermined attribute of the tuple before integrating the tuple into the
join view.
|