got it, i was confused because you mentioned something about read replicas, but for my use case it s
got it, i was confused because you mentioned something about read replicas, but for my use case it sounds like D1 is the way to go.
env.DB still and work great--bundleAPI Request Failed: GET /api/v4/accounts/{ACCOUNT_ID}/d1/database/{DATABASE_ID}/table (500). /d1/database/dc00d2ec-2c06-460d-a6e4-01cfe42f93e4 on the dashboardwrangler d1 execute --jsonwrangler d1 list --json

.run() is for inserts and deletes, but I notice that it has a results property on the return type which is never actually used. When I try to use the RETURN statement in SQL I never get results, unlike running the same insert query with .all().
.batch() when the statements have more than one return type? For example .batch<T1, T2>(stmt_1, stmt_2)? Or does .batch() expect queries with homogeneous return types?env.DB--bundleAPI Request Failed: GET /api/v4/accounts/{ACCOUNT_ID}/d1/database/{DATABASE_ID}/table (500)/d1/database/dc00d2ec-2c06-460d-a6e4-01cfe42f93e4wrangler d1 execute --jsonwrangler d1 list --json.run()RETURN.all().batch().batch().batch<T1, T2>(stmt_1, stmt_2)