Trigger updating same table oracle
The block_id is not known at that time, it gets generated after the update of the rows with a trans_id. You missunderstood me i think, the block_id gets generated and that is what gets updated back.
The block_id is not known at that time, it gets generated after the update of the rows with a trans_id. The first update that you are doing is done manually is it?
Sadly I can't get at the code that does this, otherwise it would have been easy.
I would just have called the procedure from within the erp-packet interface.
Hi, I'm stuck on this problem and I can't find a sollution. 1 After certain rows get updated with a certain value. And they do not have a certain order, but after the update they all have the same trans_id. 2 I select select the rows using the value that just got updated (trans_id), this way I know wich rows I needed to select, the value is the same for all the rows that I need.
3 I then call a procedure that generates a block_id for each row, I use a table to store this block_id. 4 But the problem is that I want to update the unload_details_tab with the values from temptable.
August 02, 2005 - pm UTC did you read the referenced chapter, it'll REALLY (honest!Dear All, I have a table in which there are fields like Quantity, Price, Total etc. We have an interface where user can change the quantity (only quantity). How will I know for which row the quantity is updated..? I want to write a trigger on this table which calculates Total (qty * price) whenever qantity is updated. So, confused by your request there." What if we have a trigger for each row and write rowid along with some unique transaction id, by using a sequence, to a logging table and have after trigger for statement update that logging table rows where the for each row trigger was fired more than once. November 30, 2004 - pm UTC dbms_job use things in triggers that are transactional. ); end; call dbms_job and ask it to send the mail right after you commit. I read this link and you suggested to use some package do it. The parent table already has a Before Insert or Update trigger to insert the PK sequence value and the create date,last update date columns.For example, if the triggeer for each row is being used to send out e-mail, by using the above approach we can make sure that actual e-mail was sent out only once. If you roll back (or get rolled back), it'll un-queue the job and no mail will be sent. Is there any way we can order trigger execution OR Oracle has a predefined order which we can predict? IF there is some explicit order they should fire in, DO NOT put them into separate triggers (that would not be logical even - if something has a linear order of progression, we should have some linear piece of procedural code to do it). Do I create an AFTER INSERT OR UPDATE TRIGGER to load data into History table or combine the logic in the before Insert or Update trigger.