> SQLite does the right thing > for multi-threaded applications and many use it that way - you are not > the first.
Roger, note that OP is talking about re-entrance, not thread-safety. He wants to know which functions can be called from signal handlers which can be called in the middle of some other SQLite call in the same thread. I doubt that many people use SQLite with this pattern. Pavel On Fri, Jul 10, 2009 at 8:00 PM, Roger Binns<rog...@rogerbinns.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > liubin liu wrote: >> How could I know which SQLite3's api is reentrant? > > As a general rule they all are. The documentation page for each api > gives further details and considerations. SQLite does the right thing > for multi-threaded applications and many use it that way - you are not > the first. > > http://www.sqlite.org/threadsafe.html > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkpX1ikACgkQmOOfHg372QQUyACgugrjN65qDEwEnn1c3Rkpd926 > kHgAnjrXLUd620KE6FbIPPiuKR7WpJFH > =wcje > -----END PGP SIGNATURE----- > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
