TT
select sqlite master and select (select contributes almost 10k
MMTTMMTTMT
M
BBBM
DROP TABLE IF EXISTS at the start of your schema.sql, you can then add a package.json script that runs wrangler d1 execute dbname --local --file=schema.sql to reinitialize the db as needed
DMDD
BD1PreparedStatement if we could just D1Database->exec()? I get it can be "faster" to prepare a statement and bind different values, but since CloudFlare Workers are temporary, then what's the point? If we know that our worker is always gonna execute the same single query over and over (not multiple queries), does it make a difference in performance?
KKKK
SELECT ? FROM foo;) is not what SQLite runs. SQLite has to compile that and run it.K??1 it doesBB
KKKBBBBBDWITH all_tables AS (SELECT name FROM sqlite_master WHERE type = 'table') SELECT at.name table_name, pti.* FROM all_tables at INNER JOIN pragma_table_info(at.name) pti ORDER BY table_name results in not authorized 7500 - which permission should be assigned to the API key?KKpragma_table_info on protected tables returned by sqlite_masterD
Iselect sqlite masterselect (selectDROP TABLE IF EXISTSwrangler d1 execute dbname --local --file=schema.sqlD1PreparedStatementD1Database->exec()SELECT ? FROM foo;?1WITH all_tables AS (SELECT name FROM sqlite_master WHERE type = 'table') SELECT at.name table_name, pti.* FROM all_tables at INNER JOIN pragma_table_info(at.name) pti ORDER BY table_namepragma_table_infosqlite_masterdb.batch([
db.insert(users).values(),
db.insert(posts).values({ userId: sql`last_insert_rowid()` })
])