Pro Oracle SQL pp 397-424 | Cite as

Transaction Processing

  • Karen Morton
  • Kerry Osborne
  • Robyn Sands
  • Riyaj Shamsudeen
  • Jared Still
Chapter

Abstract

After you use Oracle Database for a while, you might have certain expectations of how it behaves. When you enter a query, you expect a consistent result set to be returned. If you enter a SQL statement to update several hundred records and the update of one of those rows fails, you expect the entire update to fail and all rows to be returned to their prior state. If your update succeeds and you commit your work to the database, you expect your changes to become visible to other users and remain in the database, at least until the data are updated again by someone else. You expect that when you are reading data, you never block a session from writing, and you also expect the reverse to be true. These are fundamental truths about how Oracle Database operates, and after you’ve become comfortable working with Oracle, you tend to take these truths for granted.

Keywords

Oates 

Copyright information

© Karen Morton 2013

Authors and Affiliations

  • Karen Morton
    • 1
  • Kerry Osborne
    • 1
  • Robyn Sands
    • 1
  • Riyaj Shamsudeen
    • 1
  • Jared Still
    • 1
  1. 1.FLUS

Personalised recommendations