Never seen this one before - we perform an update on prod_desc, feedback tells us row was updated, we commit the changes we select the column - change did not take effect. The same user can update other columns on the table with no problems. What am I missing?
Maybe a trigger, or another user also updating the same row, directly after the commit.
hmm..we do have a trigger that automatically updates our interMedia index but I'm not sure why that would prevent changes from showing up. What I really don't understand is why it thinks it updated the row?
To my experience, sometimes you just don't know what the rows or coumns be updated are the ones you really want.
Use session audit or log miner to figure out what happened.
I'm having the same problem with same situation (I also have an update trigger), would you please tell me your solution to it if you've already done it. Thanks.
Pl. Check your trigger if there is any exception block
if DBMS_OUTPUT.PUT_LINE is used in exception block
then change it with RAISE_APPLICATION_ERROR.
check your trigger "on update of <column_name> " is correct.
use the returning command to get the values you tryed to update after the update. it works like this
set column_name = X
returning column_name [into v_x];
this works only if you update one row at a time! if not, it will not work!!!
you can also use sql%rowcount to count how many lines you updated
if you have more problems, show us a print out of the trigger
Click Here to Expand Forum to Full Width