Thank you for maintaining rusqlite, I’ve been using it for various SQLite experiments for many years now and it’s been rock solid.
I’m filing this issue following the instructions from the docs for rusqlite::vtab::VTabConnection::handle():
Warning
You should not need to use this function. If you do need to, please open an issue on the rusqlite repository and describe your use case.
My use case is that I’m looking to implement a virtual table that works similarly to FTS3 (or FTS4) where it creates "shadow" tables for storing index data as part of initialization (and then queries those tables in addition to performing direct file system operations via other callbacks). The FTS3 implementation uses the connection that comes to xCreate for executing SQL queries against such "shadow" tables. It appears that using handle() is the only way to achieve this functionality with rusqlite. Do you have any other recommendations?
Thank you for maintaining rusqlite, I’ve been using it for various SQLite experiments for many years now and it’s been rock solid.
I’m filing this issue following the instructions from the docs for
rusqlite::vtab::VTabConnection::handle():My use case is that I’m looking to implement a virtual table that works similarly to FTS3 (or FTS4) where it creates "shadow" tables for storing index data as part of initialization (and then queries those tables in addition to performing direct file system operations via other callbacks). The FTS3 implementation uses the connection that comes to
xCreatefor executing SQL queries against such "shadow" tables. It appears that usinghandle()is the only way to achieve this functionality with rusqlite. Do you have any other recommendations?