Timeline for After Update/Insert trigger sometimes fails to do its job
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 24, 2016 at 12:43 | comment | added | atokpas | Let us continue this discussion in chat. | |
| Feb 24, 2016 at 12:40 | comment | added | Mikayil Abdullayev |
In this particular case, when inserting into or updating the INT_DOC table, I don't wrap the insert or update statements in a transaction. Commit is issued right after the statement.
|
|
| Feb 24, 2016 at 12:32 | comment | added | atokpas | @Mikayil Abdullayev whats about commit statement? How are you making these transaction permanent? | |
| Feb 24, 2016 at 8:20 | comment | added | Mikayil Abdullayev | yes, @JSapkota, that's right. I'll provide the sample you asked for. | |
| Feb 24, 2016 at 7:51 | comment | added | atokpas | can you add sample row which has inserted into INT_DOC but not in DOC_IDS? | |
| Feb 24, 2016 at 7:45 | comment | added | atokpas | @Mikayil Abdullayev, So this mean you should have same number of rows in INT_DOC and DOC_IDS tables but you get the different number of rows right? | |
| Feb 24, 2016 at 7:35 | comment | added | Mikayil Abdullayev |
Yeah, I know that in the third update you won't get the DOCNUMBER inserted to DOC_IDS table. But as I've mentioned in my second edit to the question, the third case never happens. That is, DOCNUMBER never gets updated. It's assigned a value inside the BEFORE UPDATE/INSERT trigger and it's never updated anywhere else again.
|
|
| Feb 24, 2016 at 6:01 | history | answered | atokpas | CC BY-SA 3.0 |