No, something we are looking at later this year. D1 is still in alpha and we are focused on stabilit
No, something we are looking at later this year. D1 is still in alpha and we are focused on stability & larger DBs first.
wrangler d1 execute --command="PRAGMA table_list" against it? Please provide errors.multipart/form-data - applies to both the Upload Module & script content endpoints. I know other folks are using this in prod but wasn’t sure if we had formally published it.
--no-bundle which is basically what you're doing with the API, and allows 'proper' dynamic importsSELECT * FROM content WHERE json_extract(data, '$.status') = 1
__D1_BETA__D1_DB rather than D1_DB that i have specified as the binding in the settings. what could be causing this?3.4.0 rather than 3.5.1?order by id desc?'SELECT * FROM content WHERE json_extract(data, "$.s") IN (0,1) AND json_extract(data, "$.t") IN (0) ORDER BY id DESC LIMIT 10 OFFSET 10' and it worked.order by end of the query, it does not work. Anyways, thanks again.__D1_BETA_ is being added as a prefix in the environment, but not binding named DB__D1_BETA_DB, but it tells me that there is no function prepare on it.DB variable is hanging on the env that i can call prepare on. any ideas?wrangler d1 backup create <db> throws Experimental DBs do not support backups yet--persist-to=./path-to-persist-db is not working as expected.

REAL valuewrangler d1 execute --command="PRAGMA table_list"multipart/form-data--no-bundleSELECT * FROM content WHERE json_extract(data, '$.status') = 1__D1_BETA__D1_DBD1_DB3.4.03.5.1order by id desc'SELECT * FROM content WHERE json_extract(data, "$.s") IN (0,1) AND json_extract(data, "$.t") IN (0) ORDER BY id DESC LIMIT 10 OFFSET 10'__D1_BETA_binding name: DB
env contains: __D1_BETA_DB__D1_BETA_DBwrangler d1 backup create <db>--persist-to=./path-to-persist-dbREAL