User Comments

According to dll.c:
Within win32, LibMain calls mysql_thread_init() and mysql_thread_end() automatically for each newly created thread after the lib has been loaded.
Therefor it shouldn't be necessary to call these functions again. As I said, only for win32 and only if we use the dynamic library.

mysql_thread_init() did crash on my machine, did investigate as mysql_init() is doing it for me.

MORE IMPORTANT remember that:

1) A new thread NEED a SPECIFIC new MYSQL* handle.
So need a call mysql_init() WITHIN your new thread.
(libmysql work badly with exotic error if you use MYSQL* handle from another thread)

Also check
if (!mysql_thread_safe()) {
m_strErrorMessage = "Thread Safe OFF: ";
ASSERT(0); // Major problem: libmysqlcompiled ThreadSafe?
}

2) you NEED EXPLICTELY to call mysql_thread_end() !!
Do it once you release mysql_close(MYSQL*..)
Or you will get Handle leak !!
(which is as bad as memory leak!)

So no bugs but if multithread carefully read API doc

For reference our destructor of our generci MySqL handler object.

HCMySQL::~HCMySQL()
{
if (m_poMySQLHandle && m_bConnection ){ // Did we use it?
mysql_close(m_poMySQLHandle) ;
mysql_thread_end(); //or 3 Handle leak!
}
if (--s_ref==0){ // incremented in ::Connect
mysql_library_end();
}
}

Add your own comment.