You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to properly support shadow tables or more advanced SQLite extensions, sqlite-loadable will need to expose some SQLite C APIs like sqlite3_prepare_v2() + sqlite3_step() + sqlite3_column_*(). That way, extensions can call CREATE TABLE xyz_foo() or INSERT INTO xyz_foo or SELECT * FROM xyz_foo for shadow tables or other more advanced usecases.
In order to properly support shadow tables or more advanced SQLite extensions,
sqlite-loadable
will need to expose some SQLite C APIs likesqlite3_prepare_v2()
+sqlite3_step()
+sqlite3_column_*()
. That way, extensions can callCREATE TABLE xyz_foo()
orINSERT INTO xyz_foo
orSELECT * FROM xyz_foo
for shadow tables or other more advanced usecases.This will unblock a few features/extensions:
sqlite-ml
parquet_storage
vtab insqlite-parquet
xsv_store
insqlite-xsv
?sqlite-docs
Planned API features:
Statement
struct that prepares asqlite3_stmt
sqlite3_prepare_v2
)sqlite3_bind_*()
)sqlite3_step
) (sqlite3_column_*()
)sqlite3_mprintf()
in rust for easier/safer string escaping, for shadow table creationsThe text was updated successfully, but these errors were encountered: