It looks to me as if the query optimizer gets confused to have INSERT and UPDATE to the SAME table in sequence.
If they both run well when separated I'd suggest calling both in sequence.
From code or performance, I see no advantage to pack them together. Rather the opposite.
- Log in to post comments
.png)
.png)
.png)
.png)