Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Mon, 23 Nov 2015 @ 20:53:15 GMT

  <Prev Next>  
Next> Last>>  

Subj:   On ANSI mode, how locks are handled when commit is not performed after update
From:   Ganga, Sandeep Kumar

Hi Forum,

     session transaction mode=ansi
     .logon usera
     select session;--123456
     create multiset table t2(a int);
     insert into t2(1);
     insert into t2(2);
     insert into t2(3);
     insert into t2(4);

     select * from t2;
     results: 1,2,3,4

     update t2 set a=9 where a=1;

no commit done after update

on otherhand, logged on with the same user.

     .logon usera
     select session;---567890
     select * from t2 where a>2;

here lock is on complete table, instead lock to be on one single row.(on select other than a=1 would have been outputted, but not) why remaining rows are not shown up on select and can someone shed some light how locks handled on update statement.




  <Prev Next>  
Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 24 Jul 2020