Results 1 to 3 of 3

Thread: Cur_commit

  1. #1
    Join Date
    Dec 2011
    Posts
    30

    Unanswered: Cur_commit

    If I am using CUR_COMMIT parameter then can DIRTY READ phenomenon occurs?

    If yes, Then can we say this is the new definition of CURSOR statbility level??

  2. #2
    Join Date
    Sep 2004
    Location
    Belgium
    Posts
    1,126
    Non-committed changes are always exclusively locked, and CUR_COMMIT never reads locked rows, so the answer is no: dirty reads are impossible with cursor stability.
    Beware though that a thread may read its own dirty rows...
    --_Peter Vanroose,
    __IBM Certified Database Administrator, DB2 9 for z/OS
    __IBM Certified Application Developer
    __ABIS Training and Consulting
    __http://www.abis.be/

  3. #3
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    What is your definition of "dirty read"?
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •