Ethan Funk <et...@redmountainradio.com> was heard to say: > Even with libdbi linked against the libmysqlclient_r library, the > API is not thread safe with out the mysql_thread_start() and > mysql_thread_end() calls on a **shared** connection, so including my > change would not **hurt**. Linking agains the non _r library and > you can't even run different connection on different threads. >
Would it be feasible to tell the libdbi driver how your app uses threads by means of a driver option? Something like mysql_one_conn_per_thread? This way, the driver could use some optimizations like yours which apply only under these particular conditions. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Libdbi-drivers-devel mailing list Libdbi-drivers-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel
