if in my wrangler.toml file i put a `database_id` and a different `preview_database_id` (one is call

V

veequeOP•8/17/24, 1:36 PM

also, migrations stored in the

migrations

migrations

migrations

migrations folder don't get applied automatically if someone pushes a new sql file, right? if that's the case however, how can i disable that behaviour?

HHard@Work You could make the queries via the D1 API? It's quite a bit slower, but I would ...

J

jacoblukewood•8/17/24, 1:50 PM

great idea. thank you

Vveeque if in my wrangler.toml file i put a `database_id` and a different `preview_datab...

H

Hard@Work•8/17/24, 1:53 PM

In local mode?

Vveeque also, migrations stored in the `migrations` folder don't get applied automatical...

H

Hard@Work•8/17/24, 1:53 PM

I don't think there is a setting to have the automatically applied. I think you need to run the migrations yourself manually

X

X•8/17/24, 6:11 PM

h

O

Ottomated•8/18/24, 1:19 AM

Anyone know why BLOB fields return

number[]

number[]

number[]

number[] instead of

ArrayBuffer

ArrayBuffer

ArrayBuffer

ArrayBuffer? Seems weird because the docs show that they should map to ArrayBuffers.

FFini I ❤️ Cloudflare My production D1 has been down for 2 days and still no reply on ...

W

Walshy•8/18/24, 12:13 PM

what's your ticket id?

W

Walshy•8/18/24, 12:41 PM

I've escalated it to support to check on

S

shellsort•8/18/24, 3:16 PM

Using rusts prepare and all functions, I execute an sql statement in my scheduled worker using the --test-scheduled flag of wrangler and then running

curl "http://localhost:8787/__scheduled?cron=*+*+*+*+*"

curl "http://localhost:8787/__scheduled?cron=*+*+*+*+*"

curl "http://localhost:8787/__scheduled?cron=*+*+*+*+*"

curl "http://localhost:8787/__scheduled?cron=*+*+*+*+*"

to simulate a scheduled event instantly.

This returns an error:

Error: Error: D1_ERROR: no such table: image: SQLITE_ERROR - Cause: Error: D1_ERROR: no such table: image: SQLITE_ERROR

Error: Error: D1_ERROR: no such table: image: SQLITE_ERROR - Cause: Error: D1_ERROR: no such table: image: SQLITE_ERROR

Error: Error: D1_ERROR: no such table: image: SQLITE_ERROR - Cause: Error: D1_ERROR: no such table: image: SQLITE_ERROR

Error: Error: D1_ERROR: no such table: image: SQLITE_ERROR - Cause: Error: D1_ERROR: no such table: image: SQLITE_ERROR

When executing the same statement via the REST API I get the expected result.

I tried wrapping the table name in ' ' marks, but get the same result.

Does anyone have an idea?
Yes it's the same database. Yes I double checked the table name.

S

shellsort•8/18/24, 3:18 PM

It's a really simple sql statement too. No joins or anything like that happening. Just good old select x from y when z.

S

shellsort•8/18/24, 4:04 PM

-> Fixed. Resolve was using the --remote flag/creating a local dev d1 db.

M

moonchav•8/18/24, 7:26 PM

is it possible to bind multiple D1 dbs to a single worker? And is it possible to bind a single D1 db to multiple workers?

Mmoonchav is it possible to bind multiple D1 dbs to a single worker? And is it possible to...

I

Isaac McFadyen•8/18/24, 7:26 PM

Yes and yes

I

Isaac McFadyen•8/18/24, 7:26 PM

Just bind it like normal in your wrangler.toml but specify multiple of them

M

moonchav•8/18/24, 7:27 PM

oh sweet, thank you! I should have just rolled the dice and tried it before asking

I

Isaac McFadyen•8/18/24, 7:27 PM

No problem :lul:

V

veequeOP•8/19/24, 1:47 PM

in my

wrangler.toml

wrangler.toml

file I have this:

[[d1_databases]]
binding = "db"
database_name = "prod-main"
database_id = "[uuid1]"
preview_database_id = "[uuid2]"

[[d1_databases]]
binding = "db"
database_name = "prod-main"
database_id = "[uuid1]"
preview_database_id = "[uuid2]"

[[d1_databases]]
binding = "db"
database_name = "prod-main"
database_id = "[uuid1]"
preview_database_id = "[uuid2]"

[[d1_databases]]
binding = "db"
database_name = "prod-main"
database_id = "[uuid1]"
preview_database_id = "[uuid2]"

(it's a sveltekit app) however the preview deployments still use the production database... I thought that setting the

preview_database_id

preview_database_id

to the uuid of the preview database would suffice, but apparently it doesn't. In the D1 documentation I could only find https://developers.cloudflare.com/d1/configuration/environments/ but the config used looks vastly different than mine. what do I have to do?

Vveeque in my `wrangler.toml` file I have this: ``` [[d1_databases]] binding = "db" dat...

H

Hard@Work•8/19/24, 1:51 PM

IIRC preview IDs aren't used for anything on pages. You need to add a

database_id

database_id

to the preview env

V

veequeOP•8/19/24, 1:51 PM

and that env is set to be the staging one by preview deployments without me having anything to do, right?

V

veequeOP•8/19/24, 1:58 PM

ah ok, i see now, ty

V

veequeOP•8/19/24, 1:59 PM

can a d1 db be renamed?

FFini Thanks, I appreciate it. It's a production system that's now been done for 2 day...

W

Walshy•8/19/24, 6:20 PM

You should be good now, apologies for the issue!

カ

カイル•8/20/24, 5:00 AM

Is it possible to use the D1 rest API but lockdown the API key to only that D1 database

WWalshy You should be good now, apologies for the issue!

D

Dean•8/20/24, 10:06 AM

What was the cause? Deploying a ton of databases and this has me concerned

カカイル Is it possible to use the D1 rest API but lockdown the API key to only that D1 d...

D

Dean•8/20/24, 10:20 AM

Better off using a worker with an API Key.

V

veequeOP•8/20/24, 11:25 AM

this is my

wrangler.toml

wrangler.toml

:

name = "[the name]"
compatibility_date = "2024-07-29"
pages_build_output_dir = ".svelte-kit/cloudflare"

[[env.production.d1_databases]]
binding = "db"
database_name = "prod-main"
database_id = "524d4c4f-410b-46f9-9a87-2dc4f6110b1c"

[[env.preview.d1_databases]]
binding = "db"
database_name = "dev-main"
database_id = "025df237-d405-4f57-859f-ad3a055fd74b"

name = "[the name]"
compatibility_date = "2024-07-29"
pages_build_output_dir = ".svelte-kit/cloudflare"

[[env.production.d1_databases]]
binding = "db"
database_name = "prod-main"
database_id = "524d4c4f-410b-46f9-9a87-2dc4f6110b1c"

[[env.preview.d1_databases]]
binding = "db"
database_name = "dev-main"
database_id = "025df237-d405-4f57-859f-ad3a055fd74b"

name = "[the name]"
compatibility_date = "2024-07-29"
pages_build_output_dir = ".svelte-kit/cloudflare"

[[env.production.d1_databases]]
binding = "db"
database_name = "prod-main"
database_id = "524d4c4f-410b-46f9-9a87-2dc4f6110b1c"

[[env.preview.d1_databases]]
binding = "db"
database_name = "dev-main"
database_id = "025df237-d405-4f57-859f-ad3a055fd74b"

name = "[the name]"
compatibility_date = "2024-07-29"
pages_build_output_dir = ".svelte-kit/cloudflare"

[[env.production.d1_databases]]
binding = "db"
database_name = "prod-main"
database_id = "524d4c4f-410b-46f9-9a87-2dc4f6110b1c"

[[env.preview.d1_databases]]
binding = "db"
database_name = "dev-main"
database_id = "025df237-d405-4f57-859f-ad3a055fd74b"

and when I try to run

wrangler d1 migrations apply prod-main --local

wrangler d1 migrations apply prod-main --local

wrangler d1 migrations apply prod-main --local

wrangler d1 migrations apply prod-main --local (or even without

--local

--local

) it says:

 ⛅️ wrangler 3.72.0
-------------------

✘ [ERROR] Couldn't find a D1 DB with the name or binding 'prod-main' in wrangler.toml.

 ⛅️ wrangler 3.72.0
-------------------

✘ [ERROR] Couldn't find a D1 DB with the name or binding 'prod-main' in wrangler.toml.

 ⛅️ wrangler 3.72.0
-------------------

✘ [ERROR] Couldn't find a D1 DB with the name or binding 'prod-main' in wrangler.toml.

 ⛅️ wrangler 3.72.0
-------------------

✘ [ERROR] Couldn't find a D1 DB with the name or binding 'prod-main' in wrangler.toml.

is it because of the way I've set up the environment variables?

V

veequeOP•8/20/24, 11:26 AM

it works just fine when running on cloudflare itself

Vveeque this is my `wrangler.toml`: ```toml name = "[the name]" compatibility_date = "2...

H

Hard@Work•8/20/24, 11:26 AM

You probably want

wrangler d1 migrations apply prod-main -e production --local

wrangler d1 migrations apply prod-main -e production --local

wrangler d1 migrations apply prod-main -e production --local

wrangler d1 migrations apply prod-main -e production --local

V

veequeOP•8/20/24, 11:27 AM

yup, that was it, thanks!

V

veequeOP•8/20/24, 11:49 AM

Well now it seems like the fact that I have a

preview

preview

and a

production

production

environment variable has made it not work locally inside the svelte kit app this is my

app.d.ts

app.d.ts

app.d.ts

app.d.ts

interface Platform {
  env: {
    db: D1Database;
  };
}

interface Platform {
  env: {
    db: D1Database;
  };
}

interface Platform {
  env: {
    db: D1Database;
  };
}

interface Platform {
  env: {
    db: D1Database;
  };
}

and I use it like this:

const db = await drizzle(platform?.env.db, { schema });

const db = await drizzle(platform?.env.db, { schema });

const db = await drizzle(platform?.env.db, { schema });

const db = await drizzle(platform?.env.db, { schema });

I also tried adding a nested

production

production

variable in both

Platform

Platform

Platform

Platform and where I use it:

env.production.db

env.production.db

env.production.db

env.production.db but no dice

V

veequeOP•8/20/24, 11:50 AM

TypeError: Cannot read properties of undefined (reading 'prepare')

TypeError: Cannot read properties of undefined (reading 'prepare')

TypeError: Cannot read properties of undefined (reading 'prepare')

TypeError: Cannot read properties of undefined (reading 'prepare')

Vveeque Well now it seems like the fact that I have a `preview` and a `production` envir...

H

Hard@Work•8/20/24, 11:52 AM

It would just be

interface Platform {
  env: {
    db: D1Database;
  };
}

interface Platform {
  env: {
    db: D1Database;
  };
}

interface Platform {
  env: {
    db: D1Database;
  };
}

interface Platform {
  env: {
    db: D1Database;
  };
}

, not with environments

H

Hard@Work•8/20/24, 11:52 AM

Also note that

Unlike Workers Environments, production and preview are the only two options available via [env.<ENVIRONMENT>] on Pages

HHard@Work It would just be ```ts interface Platform { env: { db: D1Database; }; } ...

V

veequeOP•8/20/24, 11:53 AM

still doesn't work, same error

H

Hard@Work•8/20/24, 11:53 AM

Uh

V

veequeOP•8/20/24, 11:54 AM

export const GET: RequestHandler = async ({ params, platform }) => {
    if (platform === undefined) return new Response('err');
    if (params.user === undefined) return new Response('err');

    const db = await drizzle(platform?.env.db, { schema });

    const result = await db.insert(schema.users).values({ name: params.user });

    return new Response(JSON.stringify(result));
};

export const GET: RequestHandler = async ({ params, platform }) => {
    if (platform === undefined) return new Response('err');
    if (params.user === undefined) return new Response('err');

    const db = await drizzle(platform?.env.db, { schema });

    const result = await db.insert(schema.users).values({ name: params.user });

    return new Response(JSON.stringify(result));
};

export const GET: RequestHandler = async ({ params, platform }) => {
    if (platform === undefined) return new Response('err');
    if (params.user === undefined) return new Response('err');

    const db = await drizzle(platform?.env.db, { schema });

    const result = await db.insert(schema.users).values({ name: params.user });

    return new Response(JSON.stringify(result));
};

export const GET: RequestHandler = async ({ params, platform }) => {
    if (platform === undefined) return new Response('err');
    if (params.user === undefined) return new Response('err');

    const db = await drizzle(platform?.env.db, { schema });

    const result = await db.insert(schema.users).values({ name: params.user });

    return new Response(JSON.stringify(result));
};

this is the quick-and-botchy code i made for adding something to a table

V

veequeOP•8/20/24, 11:55 AM

in the

/api/create/[user]

/api/create/[user]

/api/create/[user]

/api/create/[user] route

V

veequeOP•8/20/24, 11:57 AM

const result = await db.select().from(schema.users);

const result = await db.select().from(schema.users);

const result = await db.select().from(schema.users);

const result = await db.select().from(schema.users); also doesn't query, same error

V

veequeOP•8/20/24, 11:57 AM

it seems to me like the sveltekit app is trying to load a db that wrangler provides in a different way than it expects to(?)

V

veequeOP•8/20/24, 12:00 PM

putting a console.log to see what platform contains it shows me

env: {},

env: {},

env: {},

env: {},... so it's not loading anything

V

veequeOP•8/20/24, 12:02 PM

ok found the issue: in the

svelte.config.js

svelte.config.js

file i had to set

platformProxy.environment

platformProxy.environment

to

'production'

'production'

inside the adapter's config

Vveeque ok found the issue: in the `svelte.config.js` file i had to set `platformProxy.e...

H

Hello, I’m Allie!•8/20/24, 12:12 PM

Good you figured it out! I’d kind of stumped myself on that one

if in my wrangler.toml file i put a `database_id` and a different `preview_database_id` (one is call

Similar Threads

Similar Threads

Similar Threads