Some hacks to avoid XenForo design issues which trigger DB errors.

XenForo's Datawriters have a _postSaveAfterTransaction() method. This method is intended to run after a database transaction is finished, but if a DataWriter is called from with-in another DataWriter, this does not happen.

This incurs the risk that various notification actions will pull in large queries into the transaction, which increasing the risk of deadlocks on a busy forum.

• Race condition for watch thread toggle
• Deadlock on conversations
• Deadlock on posts
• Deadlock on resolving/rejecting Reports

• php +5.5

Fixes a race condition when creating/removing a watch thread state

Provides a workaround for a XenForo design issue where updating conversation counters can cause deadlocks.

• rebuilding user conversation counters occurs inside a large transaction, and is deadlock prone.

Provides a workaround for a XenForo design issue where adding/removing posts can cause deadlocks.

• updating user alert counters occurs inside a large transaction, and is deadlock prone.

Provides a workaround for a XenForo design issue where adding/removing posts can cause deadlocks.

• Sends report resolve/reject alerts inside the transaction.

##Supported DataWriters

• XenForo_DataWriter_ConversationMaster
• XenForo_DataWriter_ConversationMessage
• XenForo_DataWriter_Discussion_Thread
• XenForo_DataWriter_DiscussionMessage_Post
• XenForo_DataWriter_Report
• XenForo_DataWriter_ReportComment
• XenForo_DataWriter_Warning
• XenForo_DataWriter_User