Abstract
In object-oriented database systems (OODBSs), the traditional transaction models are no longer suitable because of the difference between the object-oriented data model (OODM) and the conventional data models (e.g. relational data model). In this paper, transaction models for advanced database applications are reviewed and their shortcomings are analyzed. Exchangeability of operations is proposed instead of commuativity and recoverability for using more semantics in transaction management. As a result, an object-oriented transaction model (in short, OOTM) is presented. It is not modeled for some special application, but directly based on object-oriented paradigms. A transaction is regarded as an interpretation of a method. Each transaction (even subtransactions) keeps relative ACID (Atomicity, Consistency, Isolation, Durability) properties, therefore the special problems appearing in OODBSs such as “long transactions”, “visibility of inconsistent database state” can be solved.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
