On Wed, Jun 22, 2016 at 8:13 PM, Simon Slavin <slav...@bigfraud.org> wrote: > On 23 Jun 2016, at 3:52am, mon siong <monsi...@yahoo.com> wrote: >> PHP is using sqlite3 library (http://php.net/manual/en/book.sqlite3.php) >> and C program is handle the sqlite using Serialized. >> >> Both of them are accessing the same DB at the same time . This can cause DB >> corrupt ? > > No. These two work correctly together. You should get no corruption from > using these two together.
I wonder if it would be worthwhile to provide a PRAGMA (or function) which returned a blob derived from the VFS pointer, perhaps hashed. Then you could very easily verify if multiple higher-level libraries are sharing the same underlying sqlite library, because that operation would return the same result in both cases. I'm suggesting to derive from the VFS pointer because if separate sqlite libraries were sharing the same Unix VFS I think the POSIX locking problem would not occur. sqlite_source_id() is _really_ close, but technically could be identical for distinct sqlite libraries linked into the same process. Sorry if I'm too tired to make sense, scott _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
