I'm still curious as to how you called .insert, can you link me to where they go over that? I don'

KKJolibois I'm still curious as to how you called .insert, can you link me to where they go...

B

bun•2/29/24, 9:32 PM

Its drizzle orm

K

KJoliboisOP•2/29/24, 9:33 PM

thank you @nora and @bun

Ggeelen sadly no. Out of interest, what's your use-case?

T

Tony Leung•3/1/24, 4:37 AM

i guess that he wants to terminate the execution if it does not finish online. In mysql they have query hint like:

SELECT /*+ MAX_EXECUTION_TIME(1000) */ --in milliseconds * FROM table

SELECT /*+ MAX_EXECUTION_TIME(1000) */ --in milliseconds * FROM table

SELECT /*+ MAX_EXECUTION_TIME(1000) */ --in milliseconds * FROM table

SELECT /*+ MAX_EXECUTION_TIME(1000) */ --in milliseconds * FROM table

T

Tony Leung•3/1/24, 4:47 AM

since workers only lives for 30 seconds per fetch invocation, i guess he want it failed rather than worker eviction to raise a reasonable error to the user, or to do something else

TTony Leung since workers only lives for 30 seconds per fetch invocation, i guess he want it...

H

Hello, I’m Allie!•3/1/24, 5:52 AM

That’s 30 seconds of CPU time, not wall time

H

Hello, I’m Allie!•3/1/24, 5:52 AM

So even if the response takes longer than 30 seconds, it should still complete

HHello, I’m Allie!That’s 30 seconds of CPU time, not wall time

T

Tony Leung•3/1/24, 5:53 AM

Oh that's new, i thought bundle workers only have 30s off wall time

TTony Leung Oh that's new, i thought bundle workers only have 30s off wall time

H

Hello, I’m Allie!•3/1/24, 5:54 AM

Nope:

HHello, I’m Allie!Nope:

T

Tony Leung•3/1/24, 5:54 AM

Oh nice!

T

Tony Leung•3/1/24, 5:54 AM

Thanks

T

Tony Leung•3/1/24, 5:55 AM

Didn't know that they dont limit wall time. I remembered that in a doc workers will have a high chance of eviction if they run pass 30s

TTony Leung Didn't know that they dont limit wall time. I remembered that in a doc workers w...

H

Hello, I’m Allie!•3/1/24, 6:09 AM

That one is sort of true. As you pass the 30 second mark, your chance of eviction goes up, but I wouldn’t say it is high…

Aalexblokh hey, D1 ninjas! is there a way to use https://developers.cloudflare.com/api/ope...

M

Max (@rozenmd)•3/1/24, 11:02 AM

not via that API, no, but you could expose a Worker as your own custom HTTP API? https://github.com/elithrar/http-api-d1-example

GitHub

GitHub - elithrar/http-api-d1-example: An example HTTP API for Clou...

An example HTTP API for Cloudflare's D1 database: https://developers.cloudflare.com/d1/

elithrar/http-api-d1-example

Aalexblokh is there a place where we can submit a feature request for a raw mode for the AP...

M

Max (@rozenmd)•3/1/24, 11:26 AM

you just did

I

impairedFelon•3/1/24, 11:28 AM

When we will able use D1 on production? After 30-40 days I will publish app on store. Can i trust current D1?

P

Patrick M•3/1/24, 1:35 PM

It would be nice if the d1 dashboard showed the performance stats for each query! It’s probably already coming through the API right? My small db is already using a lot more rows read that I would like. Would like some easier ways to investigate queries.

PPatrick M It would be nice if the d1 dashboard showed the performance stats for each query...

I

impairedFelon•3/1/24, 1:37 PM

Did u try;

npx wrangler d1 insights

npx wrangler d1 insights

npx wrangler d1 insights

npx wrangler d1 insights it shows various stats about queries.

K

kian•3/1/24, 1:37 PM

Yep, that

K

kian•3/1/24, 1:38 PM

You'll get the duration it took for D1 to run the query and the rows read/written (for billing purposes)

PPatrick M It would be nice if the d1 dashboard showed the performance stats for each query...

M

Max (@rozenmd)•3/1/24, 1:54 PM

its coming for the dash, too

IimpairedFelon Did u try; `npx wrangler d1 insights` it shows various stats about queries.

M

Max (@rozenmd)•3/1/24, 1:55 PM

for now there's this

M

Max (@rozenmd)•3/1/24, 1:55 PM

will also be able to recommend queries that need indexes

P

Patrick M•3/1/24, 1:58 PM

Yeah I used the insights. It’s very useful, thank you for adding it. I learned one of my queries read 1 million rows in the past 24h.

I just added some new indexes. Just thinking now I want to experiment with one off versions of that query to see if there is any improvement but it’s still hard to measure. Wow, I’ll be looking forward to the dash improvements!

IimpairedFelon When we will able use D1 on production? After 30-40 days I will publish app on s...

T

Tony Leung•3/1/24, 2:23 PM

How often do you read/write on your db?

C

chand1012•3/1/24, 4:44 PM

Who should I contact if I’m looking at using D1 in a production capacity and need more than a gigabyte in storage?

C

Cyb3r-Jak3•3/1/24, 4:58 PM

It should be 2 GB for beta DBs and best place for limit increases is https://forms.gle/ukpeZVLWLnKeixDu7

Google Docs

Cloudflare Developer Platform: Limit Increase Request Form

Want to increase the limits of your current plan? Let us know what your requirements are here.

V

Vy•3/1/24, 5:13 PM

Right now, we're not evaluating per-database limit increases. But we're actively working towards 10GB databases

A

anymaniax•3/1/24, 5:15 PM

We will probably rebuild a product with 5 million of users on it. It’s a chat base application which use an external provider for the chat. So the db only handle some informations about users and it’s mostly use for a community feature with a list of all users and a search on it. Do you think D1 could be a good fit for that us case? (I am a bit afraid of reaching the size limit)

U

Unsmart•3/1/24, 5:20 PM

I think a database actually built for search would probably suit that better (i.e algolia/elasticsearch/etc).

A

anymaniax•3/1/24, 5:28 PM

For the search part probably (I was also thinking using a worker ai for the search part with vectorize) but I cannot put everything in it no? I would still need something for the community part and some other features

A

ajgeiss0702•3/1/24, 7:08 PM

is there any way to see previous month's usage? I would like to get an idea what my billing will look like

A

ajgeiss0702•3/1/24, 7:10 PM

yes, but I would like to see my previous usage to see what my bill will look like in the future once it does start counting

Aajgeiss0702 yes, but I would like to see my previous usage to see what my bill will look lik...

V

Vy•3/1/24, 7:11 PM

you can do this via GraphQL API, row metrics are also available in the UI

A

ajgeiss0702•3/1/24, 7:12 PM

previous month's?

A

ajgeiss0702•3/1/24, 7:12 PM

I meant to look at the dashboard yesterday but completly forgot, so im wondering if theres any way to check that now

V

Vy•3/1/24, 7:17 PM

yes, GraphQL API has 31 day history

F

fre2mansur•3/2/24, 7:11 AM

billing enabling for d1 means, is the beta ending?

TTony Leung How often do you read/write on your db?

I

impairedFelon•3/2/24, 7:30 AM

I can't assume, it's online mobile app and highly depends to Worker and D1. But i can say I will stay in free quotas even with 1000 daily user.

T

Tony Leung•3/2/24, 7:32 AM

If you don't write much, like 10-20% write and 80% read then it's fine. Mine is 10% write and it's more than ok.

IimpairedFelon I can't assume, it's online mobile app and highly depends to Worker and D1. But ...

T

Tony Leung•3/2/24, 7:34 AM

Mine don't have more than 20CCU...

I

impairedFelon•3/2/24, 7:35 AM

Then it will fine i guess.

O

oof2win2•3/2/24, 10:22 AM

hi. so my migration just failed locally because i'm not authorized? no idea what is going on, it worked before

@oof2win2 ➜ /workspaces/fdgl/apps/server (master) $ bun wrangler d1 migrations apply fdgl-maindb --local
 ⛅️ wrangler 3.29.0 (update available 3.30.1)
-------------------------------------------------------
Migrations to be applied:
┌─────────────────────────────────────────────┐
│ name                                        │
├─────────────────────────────────────────────┤
│ 0002_change_proof_to_use_proof_id_as_id.sql │
└─────────────────────────────────────────────┘
✔ About to apply 1 migration(s)
Your database may not be available to serve requests during the migration, continue? … yes
🌀 Mapping SQL input into an array of statements
🌀 Executing on local database fdgl-maindb (fb5ec937-8f92-4532-a8c4-9d2d0abc9675) from .wrangler/state/v3/d1:
┌─────────────────────────────────────────────┬────────┐
│ name                                        │ status │
├─────────────────────────────────────────────┼────────┤
│ 0002_change_proof_to_use_proof_id_as_id.sql │ ❌       │
└─────────────────────────────────────────────┴────────┘

❌ Migration 0002_change_proof_to_use_proof_id_as_id.sql failed with the following
errors:

✘ [ERROR] not authorized

@oof2win2 ➜ /workspaces/fdgl/apps/server (master) $ bun wrangler d1 migrations apply fdgl-maindb --local
 ⛅️ wrangler 3.29.0 (update available 3.30.1)
-------------------------------------------------------
Migrations to be applied:
┌─────────────────────────────────────────────┐
│ name                                        │
├─────────────────────────────────────────────┤
│ 0002_change_proof_to_use_proof_id_as_id.sql │
└─────────────────────────────────────────────┘
✔ About to apply 1 migration(s)
Your database may not be available to serve requests during the migration, continue? … yes
🌀 Mapping SQL input into an array of statements
🌀 Executing on local database fdgl-maindb (fb5ec937-8f92-4532-a8c4-9d2d0abc9675) from .wrangler/state/v3/d1:
┌─────────────────────────────────────────────┬────────┐
│ name                                        │ status │
├─────────────────────────────────────────────┼────────┤
│ 0002_change_proof_to_use_proof_id_as_id.sql │ ❌       │
└─────────────────────────────────────────────┴────────┘

❌ Migration 0002_change_proof_to_use_proof_id_as_id.sql failed with the following
errors:

✘ [ERROR] not authorized

@oof2win2 ➜ /workspaces/fdgl/apps/server (master) $ bun wrangler d1 migrations apply fdgl-maindb --local
 ⛅️ wrangler 3.29.0 (update available 3.30.1)
-------------------------------------------------------
Migrations to be applied:
┌─────────────────────────────────────────────┐
│ name                                        │
├─────────────────────────────────────────────┤
│ 0002_change_proof_to_use_proof_id_as_id.sql │
└─────────────────────────────────────────────┘
✔ About to apply 1 migration(s)
Your database may not be available to serve requests during the migration, continue? … yes
🌀 Mapping SQL input into an array of statements
🌀 Executing on local database fdgl-maindb (fb5ec937-8f92-4532-a8c4-9d2d0abc9675) from .wrangler/state/v3/d1:
┌─────────────────────────────────────────────┬────────┐
│ name                                        │ status │
├─────────────────────────────────────────────┼────────┤
│ 0002_change_proof_to_use_proof_id_as_id.sql │ ❌       │
└─────────────────────────────────────────────┴────────┘

❌ Migration 0002_change_proof_to_use_proof_id_as_id.sql failed with the following
errors:

✘ [ERROR] not authorized

@oof2win2 ➜ /workspaces/fdgl/apps/server (master) $ bun wrangler d1 migrations apply fdgl-maindb --local
 ⛅️ wrangler 3.29.0 (update available 3.30.1)
-------------------------------------------------------
Migrations to be applied:
┌─────────────────────────────────────────────┐
│ name                                        │
├─────────────────────────────────────────────┤
│ 0002_change_proof_to_use_proof_id_as_id.sql │
└─────────────────────────────────────────────┘
✔ About to apply 1 migration(s)
Your database may not be available to serve requests during the migration, continue? … yes
🌀 Mapping SQL input into an array of statements
🌀 Executing on local database fdgl-maindb (fb5ec937-8f92-4532-a8c4-9d2d0abc9675) from .wrangler/state/v3/d1:
┌─────────────────────────────────────────────┬────────┐
│ name                                        │ status │
├─────────────────────────────────────────────┼────────┤
│ 0002_change_proof_to_use_proof_id_as_id.sql │ ❌       │
└─────────────────────────────────────────────┴────────┘

❌ Migration 0002_change_proof_to_use_proof_id_as_id.sql failed with the following
errors:

✘ [ERROR] not authorized

I'm still curious as to how you called .insert, can you link me to where they go over that? I don'

Similar Threads