hello guys,
i'm having some trouble with deadlocks, that just started recently.
i have run the SHOW ENGINE INNODB STATUS command and found out that one trigger is causing this (i'm pretty sure it's the same one every time). it's an after update trigger on a table (st_orders) and it's causing a deadlock on sql's that update that table, not the same sql all the time though.
the trigger command is a monster, i'd rather not paste it here unless someone is certain they can help me fix it. i also have several more triggers and all of them gather stuff from other tables that also have triggers on them. it's a pretty messy process. but that doesn't matter all that much.
i would like to know whether the update sql that preceded the trigger would be safe to restart, or the sql has run correctly and only the trigger was rolled back?
i don't use any transactions, i only have single sql's running in my app, but i do have monster triggers all over the place.
thanks!
i'm having some trouble with deadlocks, that just started recently.
i have run the SHOW ENGINE INNODB STATUS command and found out that one trigger is causing this (i'm pretty sure it's the same one every time). it's an after update trigger on a table (st_orders) and it's causing a deadlock on sql's that update that table, not the same sql all the time though.
the trigger command is a monster, i'd rather not paste it here unless someone is certain they can help me fix it. i also have several more triggers and all of them gather stuff from other tables that also have triggers on them. it's a pretty messy process. but that doesn't matter all that much.
i would like to know whether the update sql that preceded the trigger would be safe to restart, or the sql has run correctly and only the trigger was rolled back?
i don't use any transactions, i only have single sql's running in my app, but i do have monster triggers all over the place.
thanks!