BB
H
.sqlite file. D1 in local development is just a wrapper around that .sqlite fileH
B
.wrangler directory?HBB
M
M
M
T
db.exec disabled inside pages functions? Works fine locally with wrangler, but not after deployed.T
.exec, do you get a db.exec is not a function error? I'm getting that, wondering if it's the same thing you are seeing and if you found a workaround?
M
I think what I meant was that the drizzle API doesn't provide a way to access the 
D1Database.exec methodM.prepare() nd the migrator tries to use the base sqlite-core dialect, it uses transactions which aren't supported by d1 : https://github.com/drizzle-team/drizzle-orm/blob/main/drizzle-orm/src/sqlite-core/dialect.ts#L768-L812M
K
S
JMJM
J
J
D1's REST API doesn't involve a Worker, which is why it's considerably slower above in the chat. Oy vey.J
Pd1 migrations apply <DB> and it always did a check to see if there where any new migrations to apply and applied them (if none, then did nothing).
P
V
database_id in wrangler.toml
D.wrangler/state/... but you can set the path explicitly when you start the worker with --persist-to={path}DDDS We should just remove the y-axis.
A
II
CM
.sqlite.sqlite.wranglerdb.exec.execdb.exec is not a functionD1Database.exec.prepare()D1's REST API doesn't involve a Worker, which is why it's considerably slowerd1 migrations apply <DB>database_id.wrangler/state/...--persist-to={path}import { json } from "@sveltejs/kit";
import { ACCOUNT_ID, CLOUDFLARE_API_KEY, CLOUDFLARE_EMAIL, DATABASE_ID } from '$lib/server/secrets.js';
/** @type {import('./$types').RequestHandler} */
export async function GET({ platform }) {
const url = `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/d1/database/${DATABASE_ID}/query`;
const options = {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'X-Auth-Email': CLOUDFLARE_EMAIL,
'X-Auth-Key': CLOUDFLARE_API_KEY
},
body: '{"sql":"SELECT * from test"}'
};
const resp = await fetch(url, options);
const data = await resp.json();
return json(data);
}