Rechercher dans le manuel MySQL
28.7.4.3 Writing C API Threaded Client Programs
The client library is almost thread-safe. The biggest problem is
that the subroutines in sql/net_serv.cc
that read from sockets are not interrupt-safe. This was done
with the thought that you might want to have your own alarm that
can break a long read to a server. If you install interrupt
handlers for the SIGPIPE interrupt, socket
handling should be thread-safe.
To avoid aborting the program when a connection terminates,
MySQL blocks SIGPIPE on the first call to
mysql_library_init(),
mysql_init(), or
mysql_connect(). To use your own
SIGPIPE handler, first call
mysql_library_init(), then
install your handler.
If “undefined symbol” errors occur when linking
against the libmysqlclient client library, in
most cases this is because you have not included the thread
libraries on the link/compile command.
The client library is thread-safe per connection. You can let two threads share the same connection with the following caveats:
Multiple threads cannot send a query to the MySQL server at the same time on the same connection. In particular, you must ensure that between calls to
mysql_query()andmysql_store_result()in one thread, no other thread uses the same connection. You must have a mutex lock around your pair ofmysql_query()andmysql_store_result()calls. Aftermysql_store_result()returns, the lock can be released and other threads may query the same connection.If you use POSIX threads, you can use
pthread_mutex_lock()andpthread_mutex_unlock()to establish and release a mutex lock.Many threads can access different result sets that are retrieved with
mysql_store_result().To use
mysql_use_result(), you must ensure that no other thread is using the same connection until the result set is closed. However, it really is best for threaded clients that share the same connection to usemysql_store_result().
You need to know the following if you have a thread that did not create the connection to the MySQL database but is calling MySQL functions:
When you call mysql_init(),
MySQL creates a thread-specific variable for the thread that is
used by the debug library (among other things). If you call a
MySQL function before the thread has called
mysql_init(), the thread does
not have the necessary thread-specific variables in place and
you are likely to end up with a core dump sooner or later. To
avoid problems, you must do the following:
Call
mysql_library_init()before any other MySQL functions. It is not thread-safe, so call it before threads are created, or protect the call with a mutex.Arrange for
mysql_thread_init()to be called early in the thread handler before calling any MySQL function. If you callmysql_init(), it will callmysql_thread_init()for you.In the thread, call
mysql_thread_end()before callingpthread_exit(). This frees the memory used by MySQL thread-specific variables.
The preceding notes regarding
mysql_init() also apply to
mysql_connect(), which calls
mysql_init().
Traduction non disponible
Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-c-api-threaded-clients.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.
