Your account ID would also be helpful @tt for the team, thanks
Your account ID would also be helpful @tt for the team, thanks
env and ctx?ExportedHandler and Env?const db = drizzle(env.DB); everywhere they need the db. is that the way to go? or is it still possible to somehow export 1 drizzle client globally?await DB.prepare('SELECT col FROM table WHERE col1 = ?2 AND col2 = ?1 AND col3 = ?1').bind(1, 2).run()SELECT file_id FROM file WHERE ref_id = '123' shows "rows_read": 2. Does it mean that reading index is also counted as well as reading the data?npx wrangler d1 migrations --help / npx wrangler d1 migrations apply --help lists persist-to as a valid option?--help output? Also is there any way to prevent this replication? Like when does that happen? If for anyone outside of an specific region no DB access happens, does that mean no replication is happening either?There is no replication at the moment. Once it's out, we will have some control for jurisdictions once those are added for D1.
meta object, and the dashboard will show it soon as well.Or does it count rows that were checked and not returned as well?All rows read are counted. From indices, non-indices, views, etc.
if (e.message.startsWith(`D1_ERROR: UNIQUE constraint failed:`)){
throw createError({statusCode:400, statusMessage:`Your name needs to be unique`})
}