Skip to main content

PL/SQL Brain Teaser: when does a COMMIT not commit?

So your users make changes to tables (with great care and security, through your PL/SQL API), your app calls this procedure and that function. At some point along the way, a COMMIT statement is executed successfully in a user's session.

Yet that same user's session still has uncommitted changes!

Huh? How is this possible?

Think you know? Comment below!

Comments

  1. The commit was within an autonomous transaction.

    ReplyDelete
  2. commit write nowait/batch?

    ReplyDelete
  3. Autonomous Transaction :allows you to leave the context of the calling transaction, perform an independent transaction, and return to the calling transaction without affecting it's state.Hence the uncommitted changes in the users session are still significant.

    ReplyDelete
  4. Autonomous transaction! Love the brain teaser!!

    ReplyDelete
  5. Just few untested random use-cases in a hurry. Feel free to correct.
    1. Dirty data is in bulk collected collections. Processing commits in loop.
    2. View with instead of trigger. Trigger only uses partial data to update.
    3. Part of dirty data is written to a external table on really slow IO device.
    4. Distributed transaction. Part of dirty data has to be updated on some other DB.
    5. Call to external service from API with part of dirty data.
    6. Trigger on table allows selective data to update?

    ReplyDelete
  6. It all depends where in the process chain the commit was executed, if there were any dml statements after it, and if any rollback (to savepoint) was executed...

    ReplyDelete
  7. And here are some thoughts offered up on LinkedIn:

    * Is the commit statement outside the procedure? It so, it may be out of scope. Is there a rollback somewhere in the procedure or function?

    * The procedure having COMMIT might have executed with autonomously. So the user changes outside that procedure are still in process and not yet committed.

    ReplyDelete
  8. And now my answer: definitely, the answer in my mind is that the COMMIT statement was executed within an autonomous transaction subprogram.

    If you include

    PRAGMA AUTONOMOUS_TRANSACTION;

    in the declaration section of your procedure or function, then a COMMIT in that subprogram will commit only those changes made in the scope of that subprogram.

    Other outstanding changes in my session will NOT be committed.

    Now as to your comments:

    @stanley, I'd love to hear more explanation about some of your items, as they are outside my area of expertise. I am not sure if a distributed xaction applies here, since I reference the "user's session".

    @john, certainly any DML statements executed after the commit would be uncommitted. ROLLBACK TO before the commit would remove outstanding changes. After the commit? Well, the teaser has to do with state of session right after the commit (implied: before other actions take place).

    Thanks for participating!

    ReplyDelete

Post a Comment

Popular posts from this blog

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p

The differences between deterministic and result cache features

 EVERY once in a while, a developer gets in touch with a question like this: I am confused about the exact difference between deterministic and result_cache. Do they have different application use cases? I have used deterministic feature in many functions which retrieve data from some lookup tables. Is it essential to replace these 'deterministic' key words with 'result_cache'?  So I thought I'd write a post about the differences between these two features. But first, let's make sure we all understand what it means for a function to be  deterministic. From Wikipedia : In computer science, a deterministic algorithm is an algorithm which, given a particular input, will always produce the same output, with the underlying machine always passing through the same sequence of states.  Another way of putting this is that a deterministic subprogram (procedure or function) has no side-effects. If you pass a certain set of arguments for the parameters, you will always get

My two favorite APEX 5 features: Regional Display Selector and Cards

We (the over-sized development team for the PL/SQL Challenge - myself and my son, Eli) have been busy creating a new website on top of the PLCH platform (tables and packages): The Oracle Dev Gym! In a few short months (and just a part time involvement by yours truly), we have leveraged Oracle Application Express 5 to create what I think is an elegant, easy-to-use site that our users will absolutely love.  We plan to initially make the Dev Gym available only for current users of PL/SQL Challenge, so we can get feedback from our loyal user base. We will make the necessary adjustments and then offer it for general availability later this year. Anyway, more on that as the date approaches (the date being June 27, the APEX Open Mic Night at Kscope16 , where I will present it to a packed room of APEX experts). What I want to talk about today are two features of APEX that are making me so happy these days: Regional Display Selector and Cards. Regional Display Sel