On 6 Oct 2015, at 2:51pm, Dominique Devienne <ddevienne at gmail.com> wrote:
> On the first connection, we declare the virtual module and its virtual > tables. This also adds the vtables to sqlite_master. But then on additional > connections to that same in-memory DB, we also need to declare a vmodule > and vtables, right? Yet it's already in sqlite_master, and it fails on the > "create virtual table" statement. > > Is this use case supported by SQLite? > Has any one tried this successfully? > Any chance this might work in the near future? Whether this works correctly depends on how your Virtual Module is written. It should be possible to implement this correctly, but I can imagine a virtual system written quickly which does not take the care to get this right. There are also things Virtual Tables can't do. For instance you cannot index a Virtual Table using SQL commands. Simon.
