Core/DBLayer: Move some syncrhonisation error prone methods into the guarded scope in MySQLConnection:Execute(PreparedStatement*)

--HG--
branch : trunk
This commit is contained in:
Machiavelli
2010-09-05 10:34:46 +02:00
parent f769e88f5c
commit 1608ebf7bf
@@ -190,15 +190,15 @@ bool MySQLConnection::Execute(PreparedStatement* stmt)
return false; return false;
uint32 index = stmt->m_index; uint32 index = stmt->m_index;
MySQLPreparedStatement* m_mStmt = GetPreparedStatement(index);
ASSERT(m_mStmt); // Can only be null if preparation failed, server side error or bad query
m_mStmt->m_stmt = stmt; // Cross reference them for debug output
stmt->m_stmt = m_mStmt;
{ {
// guarded block for thread-safe mySQL request // guarded block for thread-safe mySQL request
ACE_Guard<ACE_Thread_Mutex> query_connection_guard(m_Mutex); ACE_Guard<ACE_Thread_Mutex> query_connection_guard(m_Mutex);
MySQLPreparedStatement* m_mStmt = GetPreparedStatement(index);
ASSERT(m_mStmt); // Can only be null if preparation failed, server side error or bad query
m_mStmt->m_stmt = stmt; // Cross reference them for debug output
stmt->m_stmt = m_mStmt; // TODO: Cleaner way
stmt->BindParameters(); stmt->BindParameters();
MYSQL_STMT* msql_STMT = m_mStmt->GetSTMT(); MYSQL_STMT* msql_STMT = m_mStmt->GetSTMT();