I was talking more about the case where you want to have several D1 dbs so that you have several wri

Rrodrigo I was talking more about the case where you want to have several D1 dbs so that ...

M

then yeah,

request.cf

request.cf

has the data you need: https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties

M

Max (@rozenmd)•11/30/23, 2:53 PM

...yet

AAkthar What is the limit on number of databases we can create? i can see it's 50k in do...

M

Matt Silverlock•11/30/23, 6:54 PM

Support for more than 100,000+ databases for Workers for Platforms users — there’s no limit, but if we said “unlimited” you might not believe us — on top of the 50,000 databases per account that D1 already enables.

From https://blog.cloudflare.com/d1-open-beta-is-here/

The Cloudflare Blog

D1: open beta is here

D1 is now in open beta, and the theme is “scale”: with higher per-database storage limits and the ability to create more databases, we’re unlocking the ability for developers to build production-scale applications on D1

G

GuillaumeLakano•11/30/23, 8:47 PM

Hi! When D1 return an error because of a constraint, we doesn't receive the 'meta' object with the rows_read / rows_written, could you confirm we're not billed in this kind of errors please?

GGuillaumeLakano Hi! When D1 return an error because of a constraint, we doesn't receive the 'met...

M

Matt Silverlock•11/30/23, 11:44 PM

It can depend - this isn’t final yet and there may be cases where we should count rows read. Note that no one is actively billed just yet.

D

di_uthred•12/1/23, 4:09 AM

Hi. I want to upgrade the schema. I understand that ALTER is not supported? How do I go about executing a SQL query to move the data into the new altered table? Do I need to use wrangler to do that, or is there a way to do it from the UI?

K

kian•12/1/23, 4:18 AM

SQLite supports renaming a table, adding a new column and renaming an existing column - so that subset of

ALTER TABLE

ALTER TABLE

is supported.

V

Vikash•12/1/23, 5:34 AM

It seems the JSON parse function doesn't work in query - I have

value

value

column to store some JSON data, but when I query with

json(value)

json(value)

it return the string instead the parsed JSON.

 const sqlQuery = ctx.env.DB.prepare(
    `
      SELECT key, json(value) as value, created_at, updated_at, expire_at 
      FROM Example
      Where account_id = ?
      LIMIT ?, ?`
  ).bind(authUser.account_id, offset, limit);
  const { results } = await sqlQuery.all();

 const sqlQuery = ctx.env.DB.prepare(
    `
      SELECT key, json(value) as value, created_at, updated_at, expire_at 
      FROM Example
      Where account_id = ?
      LIMIT ?, ?`
  ).bind(authUser.account_id, offset, limit);
  const { results } = await sqlQuery.all();

 const sqlQuery = ctx.env.DB.prepare(
    `
      SELECT key, json(value) as value, created_at, updated_at, expire_at 
      FROM Example
      Where account_id = ?
      LIMIT ?, ?`
  ).bind(authUser.account_id, offset, limit);
  const { results } = await sqlQuery.all();

 const sqlQuery = ctx.env.DB.prepare(
    `
      SELECT key, json(value) as value, created_at, updated_at, expire_at 
      FROM Example
      Where account_id = ?
      LIMIT ?, ?`
  ).bind(authUser.account_id, offset, limit);
  const { results } = await sqlQuery.all();

Result

[
    {
        "key": "rMDrWHc",
        "value": "{\"url\":\"https://agenty.com\",\"params\":{},\"key\":\"rMDrWHc\"}",

        "created_at": "2023-12-01 05:27:45",
        "updated_at": null,
        "expire_at": null
    }
]

[
    {
        "key": "rMDrWHc",
        "value": "{\"url\":\"https://agenty.com\",\"params\":{},\"key\":\"rMDrWHc\"}",

        "created_at": "2023-12-01 05:27:45",
        "updated_at": null,
        "expire_at": null
    }
]

[
    {
        "key": "rMDrWHc",
        "value": "{\"url\":\"https://agenty.com\",\"params\":{},\"key\":\"rMDrWHc\"}",

        "created_at": "2023-12-01 05:27:45",
        "updated_at": null,
        "expire_at": null
    }
]

[
    {
        "key": "rMDrWHc",
        "value": "{\"url\":\"https://agenty.com\",\"params\":{},\"key\":\"rMDrWHc\"}",

        "created_at": "2023-12-01 05:27:45",
        "updated_at": null,
        "expire_at": null
    }
]

I was expecting the JSON to be parsed using

json(value)

json(value)

function given in docs - https://developers.cloudflare.com/d1/learning/querying-json/#supported-functions

Query JSON · Cloudflare D1 docs

D1 has built-in support for querying and parsing JSON data stored within a database. This enables you to:

K

kian•12/1/23, 6:12 AM

The json(X) function verifies that its argument X is a valid JSON string and returns a minified version of that JSON string

K

kian•12/1/23, 6:12 AM

It doesn't turn it into a JS object, you need to do that yourself.

K

kian•12/1/23, 6:12 AM

It's a SQLite built-in function rather than something D1 specific.

Kkian It doesn't turn it into a JS object, you need to do that yourself.

V

Vikash•12/1/23, 6:58 AM

you mean the returned value can't be used in query to print in output?

K

ken•12/1/23, 12:55 PM

Hey

Does anyone know the limit of the number of statements for Batch Statements (

db.batch()

db.batch()

) on D1?

https://developers.cloudflare.com/d1/platform/client-api/#dbbatch|

I can see that the Maximum SQL statement length is

100,000 bytes (100 KB)

100,000 bytes (100 KB)

and it should apply. But is there any other limits as well?

https://developers.cloudflare.com/d1/platform/limits/

Kken Hey 👋 Does anyone know the limit of the number of statements for Batch Statemen...

M

Max (@rozenmd)•12/1/23, 1:02 PM

should be the same as a regular db.run/all, except the limits apply individually to the queries

M

Max (@rozenmd)•12/1/23, 1:02 PM

all .batch does is save you the round trips of sending your sql+params for several queries

MMax (@rozenmd)should be the same as a regular db.run/all, except the limits apply individually...

H

Hello, I’m Allie!•12/1/23, 1:10 PM

Isn’t that it though? If limits are applied to each query individually, how many queries can you make?

HHello, I’m Allie!Isn’t that it though? If limits are applied to each query individually, how many...

M

Max (@rozenmd)•12/1/23, 1:15 PM

I'm not sure we've tested it tbh, the answer is probably "however many queries it takes to crash the DO"

M

Max (@rozenmd)•12/1/23, 1:15 PM

each query is run sequentially though so it's probably a lot

MMax (@rozenmd)all .batch does is save you the round trips of sending your sql+params for sever...

K

ken•12/1/23, 1:44 PM

that makes sense, my query is throttling anyway so should be fine ,but wanted to see the upper limit. Thank you!

Original message was deleted

M

Max (@rozenmd)•12/1/23, 2:01 PM

that's an alpha db btw

M

Max (@rozenmd)•12/1/23, 2:30 PM

thats awesome

V

Village (Josef)•12/2/23, 4:49 PM

What's the fastest way to wipe a database and remigrate it all

V

Village (Josef)•12/2/23, 4:49 PM

I'd like to avoid having to manually delete 17 tables

S

senojsitruc•12/2/23, 4:53 PM

I think I managed to blow up my D1 database (4871ae1f-6808-465d-a8ea-8b404d0c4d42) yesterday between 8 - 9pm (ET). I created a support ticket (#3047705). The dashboard times out trying to list the database and says, "Failed to reach database. Please try again later." I had been very successfully testing it with a limited load and then a couple days ago I started trying additional load. And then it died. That could be coincidental, of course. I restored the data to a new database instance and got back up-and-running. If I've done something incorrect with D1, I'd like to know more details so that I can prevent this from happening again. Thanks! (D1 is great, btw.)

V

Village (Josef)•12/2/23, 5:21 PM

Just wipe and go

V

Village (Josef)•12/2/23, 5:21 PM

I ended up finding the --file for wrangler and just wrote a bunch of drop table statements

MMax (@rozenmd)should be the same as a regular db.run/all, except the limits apply individually...

F

Fun Miles•12/2/23, 6:15 PM

Is one batch query a single API call? I am hitting a maximum API call rate limit for a single worker in a CRON worker. Would batching save me?
Is it possible to batch

SELECT

SELECT

statements?

Ssenojsitruc I think I managed to blow up my D1 database (4871ae1f-6808-465d-a8ea-8b404d0c4d4...

M

Matt Silverlock•12/2/23, 6:25 PM

Well take a look. There’s nothing you should be able to do that results in your database being “stuck” - we consider those cases bugs

F

Fun Miles•12/2/23, 6:42 PM

I can confirm I am able to have an array of 'SELECT' in there. But you cannot do

DB.prepare(statment).bind(arguments...).first()

DB.prepare(statment).bind(arguments...).first()

. So the result will be an array.

F

Fun Miles•12/2/23, 6:44 PM

But how about the number of API calls it is counted as from the point of view of not getting an error of Too many API calls from a single worker ?

F

Fun Miles•12/2/23, 6:45 PM

I know if will count as as many row retrieval as I have SELECT statement (1 result per SELECT), but that's not an issue.

Original message was deleted

F

Fun Miles•12/2/23, 6:46 PM

You were able to do 100k batched queries, so it sounds like such a batch counts as one API call and not 100k, otherwise you'd have hit the limit

F

Fun Miles•12/2/23, 7:03 PM

My re-factored query worker is now rewritten and it is not hitting the API limit anymore. But some of the queries exceed CPU time. This is a problem I've hit before. The docs say a query worker or a CRON with more than 1h between execution should get 15 minutes of CPU, but clearly it is not the case. I am being killed after 32,000ms. Is this a bug in the new billing?

F

Fun Miles•12/2/23, 7:08 PM

@Matt Any idea? I should be able to work around this for a while by reducing the queue batching size but that means I can hardly trust that it won't happen again.

F

Fun Miles•12/2/23, 9:23 PM

It doesn't look like D1 side limit to me. The message from tail said:

Queue schedule-retrieval (7 messages) - Exceeded CPU Limit @ 12/2/2023, 12:03:45 PM

Queue schedule-retrieval (7 messages) - Exceeded CPU Limit @ 12/2/2023, 12:03:45 PM

FFun Miles It doesn't look like D1 side limit to me. The message from tail said: `Queue sch...

M

Matt Silverlock•12/2/23, 10:41 PM

This is related to #queues-beta - not D1.

MMatt Silverlock This is related to #queues-beta - not D1.

F

Fun Miles•12/2/23, 10:43 PM

Or CRON workers without Queues, but nobody has answered my questions there. Thought you might have better knowledge.

FFun Miles Or CRON workers without Queues, but nobody has answered my questions there. Thou...

M

Matt Silverlock•12/2/23, 10:49 PM

The documented limits are 15 minutes of wall clock time (total duration), not true CPU time, if you use Unbound, for Cron triggers & Queue consumers. Recommend keeping the discussion in the relevant channels.

F

Fun Miles•12/2/23, 10:50 PM

It does say of CPU time per invocation. Not wall clock time.

F

Fun Miles•12/2/23, 10:52 PM

What channel do I discuss Cron trigger issue?

FFun Miles What channel do I discuss Cron trigger issue?

M

Matt Silverlock•12/2/23, 11:16 PM

If this is specific to a Cron trigger, then #workers-help - best to keep your question in one place. None of this is related to D1.

H

Hearse•12/3/23, 5:05 AM

I have a couple questions:

can i query d1 from outside of pages/workers, for example (discord bot)
can i tell wrangler d1 for my local database to copy all entries from my production database

S

Shripad Krishna•12/3/23, 6:42 AM

I have an issue with D1 binding in my solid-start app. While accessing the binding from within the app, it always connects to in-memory sqlite database instead of the local persisted DB. I am using Wrangler 3. Any idea why this is happening? There is no --persist in Wrangler 3 (like in 2) so I can't tell it to look for local D1 stored database either (in .wrangler/state/v3/d1). Is there any config that I need to change/set to make the binding look for the local state instead of check in-memory?

S

Shripad Krishna•12/3/23, 6:43 AM

When I log the binding details to the console this is what I get:

    console.log(env.__D1_BETA__DB)

    console.log(env.__D1_BETA__DB)

    console.log(env.__D1_BETA__DB)

    console.log(env.__D1_BETA__DB)

D1Database {
  binding: D1DatabaseAPI {
    db: Database {
      name: ':memory:',
      open: true,
      inTransaction: false,
      readonly: false,
      memory: true
    }
  }
}

D1Database {
  binding: D1DatabaseAPI {
    db: Database {
      name: ':memory:',
      open: true,
      inTransaction: false,
      readonly: false,
      memory: true
    }
  }
}

D1Database {
  binding: D1DatabaseAPI {
    db: Database {
      name: ':memory:',
      open: true,
      inTransaction: false,
      readonly: false,
      memory: true
    }
  }
}

D1Database {
  binding: D1DatabaseAPI {
    db: Database {
      name: ':memory:',
      open: true,
      inTransaction: false,
      readonly: false,
      memory: true
    }
  }
}

Original message was deleted

H

Hearse•12/3/23, 1:35 PM

Ah okay, is it possible for my local db to copy everything from prod

Original message was deleted

H

Hearse•12/3/23, 1:38 PM

Nice, i ll do that. Currently i am using mongodb free tier but since i am transitioning to cloudflare workers, it would be best to transition to d1 and would be more performative

B

BbIsaac•12/3/23, 1:50 PM

I am have successfully implemented an FTS5 virtual table.
However, I am facing an issue with the fts5vocab module, which is resulting in an authorization error. I would appreciate your assistance in resolving this matter. Below are the details of the queries I have executed:

1.Successful Query:
Command:

npx wrangler d1 execute staging-db-web --local --command="CREATE VIRTUAL TABLE trigram_fts5 USING fts5( title, text, tokenize='trigram');"

npx wrangler d1 execute staging-db-web --local --command="CREATE VIRTUAL TABLE trigram_fts5 USING fts5( title, text, tokenize='trigram');"

npx wrangler d1 execute staging-db-web --local --command="CREATE VIRTUAL TABLE trigram_fts5 USING fts5( title, text, tokenize='trigram');"

npx wrangler d1 execute staging-db-web --local --command="CREATE VIRTUAL TABLE trigram_fts5 USING fts5( title, text, tokenize='trigram');"

2.Query Resulting in Error:
Command:

npx wrangler d1 execute staging-db-web --local --command="CREATE VIRTUAL TABLE trigram_fts5vocab USING fts5vocab('trigram_fts5', 'row');"

npx wrangler d1 execute staging-db-web --local --command="CREATE VIRTUAL TABLE trigram_fts5vocab USING fts5vocab('trigram_fts5', 'row');"

npx wrangler d1 execute staging-db-web --local --command="CREATE VIRTUAL TABLE trigram_fts5vocab USING fts5vocab('trigram_fts5', 'row');"

npx wrangler d1 execute staging-db-web --local --command="CREATE VIRTUAL TABLE trigram_fts5vocab USING fts5vocab('trigram_fts5', 'row');"

Error Message:

[ERROR] not authorized

[ERROR] not authorized

[ERROR] not authorized

[ERROR] not authorized

I am aware that FTS5 is supported in Cloudflare D1. However, I am uncertain about the support for the fts5vocab module.
Could you please confirm if this module is supported, or if it is yet to be implemented? Any guidance or suggestions to address this issue would be greatly appreciated.

D

dev.itsarun•12/3/23, 2:29 PM

Hai guys ,How to create REST API Key For D1 Read & Write ?

I was talking more about the case where you want to have several D1 dbs so that you have several wri

Similar Threads

Similar Threads

Similar Threads