Locking mechanism for materialized views in a database system
First Claim
Patent Images
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.
2 Assignments
0 Petitions
Accused Products
Abstract
A database system receives a transaction that causes a tuple to be integrated into a join view. In response to receiving the transaction, a predefined first lock is placed 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. Also, a latch or semaphore associated with a value of a predetermined attribute of the tuple is obtained before integrating the tuple into the join view.
40 Citations
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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. An article comprising at least one storage medium containing instructions that when executed cause a database system to:
-
receive a transaction that causes a tuple to be integrated into a join view; in response to receiving the transaction, place 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 obtain a latch associated with a value of a predetermined attribute of the tuple before integrating the tuple into the join view. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
-
21. A database system, comprising:
-
a storage to store an aggregate join view; and a controller to; receive a transaction that causes a tuple to be integrated into the aggregate join view; in response to receiving the transaction, place a predefined first lock on at least a portion of the aggregate join view, the predefined first lock conflicting with either a shared lock or an exclusive lock placed on the aggregate join view, but not conflicting with another predefined first lock placed on the aggregate join view; and obtain a latch associated with a value of a group-by attribute of the tuple before integrating the tuple into the aggregate join view. - View Dependent Claims (22, 23, 24)
-
Specification