Summary-Transactions
In this chapter, we looked at many aspects of transaction management in Oracle. Transactions are among the major features that set […]
Read More →In this chapter, we looked at many aspects of transaction management in Oracle. Transactions are among the major features that set […]
Read More →
It is the function of the RECO background process to resolve this issue. This is also where COMMIT and ROLLBACK with […]
Read More →
You don’t need a “begin transaction” statement in Oracle. A transaction implicitly begins with the first statement that modifies data (the […]
Read More →
In this chapter, we covered a lot of material that, at times, might not have been obvious. However, it is vital […]
Read More →
The first thing that pops out should be “Our trigger fired twice!” We had a one-row table with a BEFORE FOR […]
Read More →
Consider the following statement:SQL> Insert into t values ( 1 ); It seems fairly clear that if the statement were to […]
Read More →
Many developers have some bad habits when it comes to transactions. I see this frequently with developers who have worked with […]
Read More →
We understand that the WHERE Y=5 component, the read-consistent phase of the query, will be processed using a consistent read (query […]
Read More →
So far, we’ve looked at read consistency: Oracle’s ability to use undo information to provide nonblocking query and consistent (correct) reads. […]
Read More →
Since PL/SQL was first introduced in version 6 of Oracle, it has been transparently using an asynchronous commit. That approach has […]
Read More →