SNIP >> processed by a complied virtual machine. Threads switch at the >> machine code level, so a thread could switch between the processing >> of the 'g' and the 'i' of the first 'begin'. >> > > SQLite actually maintains a mutex per connection. Every API call > acquires this mutext and keeps it for the duration of the call. Thus no > two calls can proceed simultaneously on the same connection. > > So no, another thread cannot interfere while sqlite3_prepare call > advances from 'g' to 'i'. >
I stand corrected. John _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
