Abstract
Transactions are a fundamental feature of all databases—they are part of what distinguishes a database from a file system. And yet, they are often misunderstood and many developers do not even know that they are accidentally not using them. This chapter examines how transactions should be used in Oracle and also exposes some bad habits that may have been picked up when developing with other databases. In particular, we look at the implications of atomicity and how it affects statements in Oracle. We also discuss transaction control statements (COMMIT, SAVEPOINT, and ROLLBACK), integrity constraints, distributed transactions (the two-phase commit, or 2PC), and finally autonomous transactions.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2022 The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature
About this chapter
Cite this chapter
Kuhn, D., Kyte, T. (2022). Transactions. In: Expert Oracle Database Architecture. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-7499-6_8
Download citation
DOI: https://doi.org/10.1007/978-1-4842-7499-6_8
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-7498-9
Online ISBN: 978-1-4842-7499-6
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books