Joe Wilson <[EMAIL PROTECTED]> wrote: > > Could you add trigger support for virtual tables via a callback > of some sort? i.e., inform the SQLite engine when the virtual > table has changed in some specific way?
The SQLite engine only runs in response to API calls. TRIGGERs firing on other database connections do not provide feedback to your connection. And virtual tables do not add this capability. > > If your virtual table is read-only, should you merely have the > specific registered functions that update/delete fail, or should > you inform SQLite about the table's characteristics beforehand > via some API call? Unclear at this point. > > Are the following functions sufficient for safe multithreaded use > of virtual table sources? > > int (*xBegin)(void *pArg); > int (*xSync)(void *pArg); > int (*xCommit)(void *pArg); > int (*xRollback)(void *pArg); > int (*xIsInTrans)(void *pArg); This functions are intended to provide two-phase atomic commit, not thread safety. Thread-safety is the responsibility of the implementation. -- D. Richard Hipp <[EMAIL PROTECTED]>
