> Beginning with 3.5.0, the synchronization is built-in. You can > call SQLite APIs with abandon and everything should just work. > There are some exceptions to this noted in the C-API documentation. > But for the most part, there is no need for the application to > worry with thread locking in SQLite 3.5.
Since I don't see any explicit notes in C-API documentation, I suppose that the basic functions just work in thread-safe manner, i.e. I can safely open a DB connection, then use it in several threads that usually call sqlite3_prepare_v2(), sqlite3_open_v2(), sqlite3_step() and sqlite3_finalize(). Do I understand correctly that since 3.5 I'm only responsible for preventing obvious errors like using a prepared statement in more than 1 thread simultaneously (i.e. open it twice or more times)? Thanks for clarification, Jiri ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
