Crash after SaveToDB destroyed a character

[leak]

Mangos Version: : 0.12 rev 8569 805e4f6

Custom Patches: mtmaps, anticheat

SD2 Version: 1498

Database Name and Version: TBCDB 0.0.2.2

http://paste2.org/p/537190

Server died during Player::SaveToDB but something with the transaction went wrong which resulted in the characters row in the characters.characters table got deleted.

No, mysql is running fine and didn't crash.

Yes the character existed before and wasn't saved for the first time.

There are remains with his guid in other tables like character_spell

Isn't the transaction supposed to be rolled back once the core crashes, loses the mysql connection and leaves an unfinished transaction behind?

And of what is the crash about in the first place? (I can post the full dump if that is of any use)

[Wojta]

rev 9548, mtmaps patch and many others, http://pastebin.com/Vq60gZ44. Anyone else has this issue?

And...how can that happen? mysql server gone away?

[The_Game_Master]

Rev: 9992

I got this problem, but characters did not dissapear, just a simple crash.

Custom core: http://pastebin.com/YcvTWCzg but this is related to a clone dupe, not something i modifyed.

[Mylifesuxito]

off: im srry this is not about the topic what mtmaps does?? or what is that ?

[Razzles]

This depends on which version of MySql you're using and what options you have set. Prior to version 5.1.15 of MySql the default behavior was to rollback the entire transaction in the event of a timeout. From 5.1.15 on, the default behavior is to only rollback the last statement. Using the option innodb_rollback_on_timeout will allow full transaction rollbacks. (Link to the MySql doc on this provided.)

Hope that helps explain it.