En/na Sam Carleton ha escrit: > The idea is that the copy and nulling happens very quickly where the > sqlite3_close is more expensive, do the copy/null very quickly so that if > another thread calls Close during the first threads execution of > sqlite3_close, the second thread finds m_db null and will not call > sqlite3_close.
Unless the second thread is called between the copy and the null assignment. I think that these concurrent accesses should be protected by a critical section. Bye -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.es/ Tel. +34 93 5883004 (Ext.133) Fax +34 93 5883007 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
