Transaction management in an object-oriented database system
SIGMOD '88 Proceedings of the 1988 ACM SIGMOD international conference on Management of data
ACM Transactions on Database Systems (TODS)
ARIES/IM: an efficient and high concurrency index management method using write-ahead logging
SIGMOD '92 Proceedings of the 1992 ACM SIGMOD international conference on Management of data
Understanding the new SQL: a complete guide
Understanding the new SQL: a complete guide
Condition handling in SQL persistent stored modules
ACM SIGMOD Record
A structured approach for the definition of the semantics of active databases
ACM Transactions on Database Systems (TODS)
New standard for stored procedures in SQL
ACM SIGMOD Record
Transaction Processing: Concepts and Techniques
Transaction Processing: Concepts and Techniques
Proceedings of the Eighth International Conference on Data Engineering
Mini-Savepoints: Firewalls for Atomic Updates
Proceedings of the Fifth International Conference on Database Systems for Advanced Applications (DASFAA)
Partial rollback in object-oriented/object-relational database management systems
Proceedings of the eleventh international conference on Information and knowledge management
Partial rollback in object-oriented/object-relational database management systems with dual buffer
Information and Software Technology
| Hi-index | 0.00 |
A partial rollback of a transaction restores the state of the transaction and the database to the state in which they have been right after the savepoint to be rolled back has been established. Contributions of this paper toward the correctness of savepoints and partial rollbacks are the followings.First, a savepoint sequence number is assigned to each savepoint. According to that, without generating any savepoint log record upon establishing savepoints, all the valid savepoints of a transaction can have different savepoint sequence numbers and the order of establishment of each valid savepoint can be discriminated efficiently.Second, the lock request entries of the manual duration are not deleted from the lock table as far as some savepoints which are established after the locks are requested but before the locks are released are valid. That guarantees the correctness of savepoints and partial rollbacks under the circumstances of supporting the four transaction isolation levels of SQL2. Third, the concept of the mini-savepoint that preserves the atomicity of update operations of the SQL level is extended and adopted to triggers and stored procedures. According to that, the atomicity of triggers and stored procedures is supported and the scope of savepoint names is restricted to the internal of the corresponding triggers or stored procedures.