Transaction Processing
Karen E. Morton, Kerry Osborne, Robyn Sands, Riyaj Shamsudeen, Jared Still · Apress eBooks · 2010
After you have been using the Oracle database for a while, you might have certain expectations of how the database will behave. When you enter a query, you expect a consistent results 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 is updated again by someone else. You expect that when you are reading data, you will never block a session from writing, and you also expect that the reverse to be true. These are fundamental truths about how the Oracle database operates and once you’ve become comfortable working with Oracle, you tend to take them for granted. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.