On Wed, May 11, 2016 at 4:16 AM, Roger Binns <rogerb at rogerbinns.com> wrote: > On 10/05/16 10:42, Andrey Gorbachev wrote: >> I am a bit worried that the initialisation of 2 different versions of SQLite >> would interfere with one another. Any advice? > > There is a way to do it, [...] create a .c file that near the top has these > lines: > > #define SQLITE_API static > #define SQLITE_EXTERN static > #include "sqlite3.c" > > That causes all the SQLite non-private symbols to only have the scope of > that .c file, and not leak outside of it.
That explains how to avoid symbol mixups, to have two or more SQLite "instances" in a single process, but doesn't address the concern about POSIX locks DRH mentioned. if more than one of those same-process instances access the same file. --DD
