Where are you running the exec via wrangler dev?
Where are you running the exec via wrangler dev?
The spellfix1 virtual table is not included in the SQLite amalgamation and is not a part of any standard SQLite build. It is a loadable extension.
sqlite3CreateView calls sqlite3StartTable so it would follow the same path of attempting to create a temporary file - that's my understandingPRAGMA query_only = 1 results in attempt to write a readonly database (8) but you might be right, I can't say I've ever really used them before.TEMP from CREATE VIEW just moves it from the main database to temp as far as I can see, so I assume it's still trying to write something at the least - of which, would be on a temporary database file.temp_store to MEMORY, which conflicts with the comment - so there might be a quirk in SQLite or D1.wrangler d1 time-travel info YOUR_DATABASE ?backup works anymore on beta?beta banner. Afaik they do still intend to have a way to dump the DB at some point{
"result": null,
"success": false,
"errors": [
{
"code": 10001,
"message": "workers.api.error.content_type"
}
],
"messages": []
}{
bindings: [
{ type: 'd1_databases', database_name: name, database_id: uuid }
]
}{
bindings: [
{ type: 'd1_databases', name, namespace_id: uuid }
]
}
settings key whose value is a stringified objectTypically, you will not share presigned URLs directly with end users or browsers, as presigned URLs are used more for internal applications.
sqlite3CreateViewsqlite3StartTablePRAGMA query_only = 1attempt to write a readonly database (8)TEMPCREATE VIEWtemptemp_storeMEMORYwrangler d1 time-travel info YOUR_DATABASEbackupbeta{
"result": null,
"success": false,
"errors": [
{
"code": 10001,
"message": "workers.api.error.content_type"
}
],
"messages": []
}{
bindings: [
{ type: 'd1_databases', database_name: name, database_id: uuid }
]
}{
bindings: [
{ type: 'd1_databases', name, namespace_id: uuid }
]
}settings// TODO(someday): Allow temporary tables. Creating a temporary table actually causes
// SQLite to open a separate temporary file to place the data in. Currently, our storage
// engine has no support for this.$ wrangler d1 backup download example-db 123a81a2-ab91-4c2e-8ebc-64d69633faf1