I have a question about dynamic bindings and the "Maximum bindings per Workers script" limit describ

I have a question about dynamic bindings and the "Maximum bindings per Workers script" limit described here: https://developers.cloudflare.com/d1/platform/limits/
When dynamic bindings are introduced, will it be possible to bind more than 5,000 D1 databases to a single worker script? Or, will this limit still apply?

KKevinnn I have a question about dynamic bindings and the "Maximum bindings per Workers s...

forslunds•3/29/24, 4:13 PM

The 5.000 limit is from a filesize limit in the config file, dynamic bindings wont be affected by that

Fforslunds The 5.000 limit is from a filesize limit in the config file, dynamic bindings wo...

KevinnnOP•3/29/24, 4:14 PM

Perfect. Thanks for the reply.

Kai•3/29/24, 8:43 PM

just noticed beta badge is gone, did d1 go GA?

James•3/29/24, 8:44 PM

Who knows, maybe it's a sneak peak for next week?

Chaika•3/29/24, 8:49 PM

light mode best appearance theme

Max (@rozenmd)•3/29/24, 9:01 PM

huge if true

James•3/29/24, 10:03 PM

maybe you're hallucinating

Kai•3/29/24, 10:08 PM

https://tenor.com/view/dog-meme-gif-25326537

Tenor

arch•3/29/24, 10:09 PM

https://tenor.com/view/obi-wan-kenobi-these-are-not-the-droids-star-wars-jedi-mind-trick-gif-23067514

Tenor

Kysan•3/29/24, 11:07 PM

is that possible to use my d1 database outside of a cloudflare worker ?

James•3/30/24, 12:41 AM

There's the API: https://developers.cloudflare.com/api/operations/cloudflare-d1-query-database

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

James•3/30/24, 12:41 AM

Or you could write a Worker that interfaces with your D1 database and then hit that externally

JoeDoe•3/30/24, 6:50 AM

what does this mean?

 D1_TYPE_ERROR: Type 'bigint' not supported for value '12907242804498931'

 D1_TYPE_ERROR: Type 'bigint' not supported for value '12907242804498931'

John_rand•3/30/24, 8:23 AM

Hi folks,
I was wondering how people deal with D1 not supporting transactions on the client side when an insert of a child table needs to have the id of the parent (ie insert parent, insert many children with parent_id, or rollback)

I am thinking of 2 options:
Have an "is_orphan" column on the parent, commit, insert children and set false in a batch, and have a cleanup process scheduled for is_orphan = true.

Or have a separate "sequence" table, where the first commit monotonically increments, and then insert parent with id provided, insert children in a batch. That way though ids could exhaust if there is a bug on the client (ie getting new ids, crashing in batch)

Is there any other option?

sabin•3/30/24, 9:05 AM

Are there any multi tenant demos with d1?

Softbear•3/30/24, 12:55 PM

Hello has anyone tested the d1 driver for datagrip ?

I can't manage to make partial selects with it

The second request returns the whole user, while the first one fails at parsing

(I'm using this driver https://github.com/isaac-mcfadyen/d1-jdbc-driver/tree/main)

Miki•3/30/24, 12:55 PM

SSoftbear Hello has anyone tested the d1 driver for datagrip ? I can't manage to make pa...

Softbear•3/30/24, 2:50 PM

Looks like a known issue, too bad it's not at all maintained
https://github.com/isaac-mcfadyen/d1-jdbc-driver/issues/3

GitHub

Select anything but * seems to fail · Issue #3 · isaac-mcfadyen/d1-...

where mytable has a primary key of mykey the follow queries error: select distinct field from mytable select field from mytable They succeed in the CF D1 console. I tested 3 different tools, just t...

albyzyx•3/30/24, 2:56 PM

Hello, New to cloudflare ecosystem. I am looking for the right stack for my project. Is D1 stable enough to use on production?

D4nk•3/30/24, 3:46 PM

Anyone know whyt my D1 binding now only has a "Fetcher" property? I can use prepare anymore

D4nk•3/30/24, 4:05 PM

I have been at this for a day now, why is my D1 suddenly a Fetcher I have everything setup correct

shahzaibkhalid•3/30/24, 4:13 PM

Hello, does someone know if it's safe to commit

database_id

database_id

and

preview_database_id

preview_database_id

wrangler.toml

wrangler.toml

file?

Sshahzaibkhalid Hello, does someone know if it's safe to commit `database_id` and `preview_datab...

Cyb3r-Jak3•3/30/24, 4:14 PM

Yes.

Cyb3r-Jak3•3/30/24, 4:14 PM

Everything in the wrangler.toml file is safe to commit. Unless you have sensitive environment variables which you should use secrets for.

CCyb3r-Jak3 Everything in the wrangler.toml file is safe to commit. Unless you have sensitiv...

shahzaibkhalid•3/30/24, 4:15 PM

Thank you!!

Original message was deleted

Isaac McFadyen•3/30/24, 7:18 PM

Yeah I'm not really maintaining that library any more unfortunately. At the time I made it I had a lot of other things going on and couldn't really find the time and then never got back around to it.

Isaac McFadyen•3/30/24, 7:18 PM

I should probably either find the time or archive it

Isaac McFadyen•3/30/24, 7:18 PM

Thanks for the reminder.

RexNormous•3/31/24, 3:08 AM

Does anyone know if making requests to a D1 DB count toward the 50/1000 fetches per worker invocation limit?

JJohn_rand Hi folks, I was wondering how people deal with D1 not supporting transactions on...

Larry•3/31/24, 12:22 PM

What you are proposing is a sort of two-phase commit which would work but I don't think it's necessary. I can think of two alternatives. sqlite (and I assume D1) has a "function"

last_insert_rowid()

last_insert_rowid()

https://www.sqlite.org/c3ref/last_insert_rowid.html. That would allow you to insert one child with the parent. If you really want to insert more than one, then do the child inserts into a temporary table and delete as you move over to the real child table. I'm sure you could find an example of this on Stack Overflow. The second alternative would be to use a GUID that you generate client-side for your primary key. That doesn't take advantage of SQLite's really cool auto-increment rowid capability but that's really a nice-to-have.

Isaac McFadyen•3/31/24, 2:46 PM

In general the SQLite project actually recommends staying away from autoincrement on rowids because it imposes extra CPU/memory constraints, and recommends either leaving it as default (which will auto increment but also reuse the IDs of deleted rows) or using a UUID.

https://www.sqlite.org/autoinc.html

The AUTOINCREMENT keyword imposes extra CPU, memory, disk space, and disk I/O overhead and should be avoided if not strictly needed. It is usually not needed.

Isaac McFadyen•3/31/24, 2:47 PM

AUTOINCREMENT literally just prevents reuse of row IDs from deleted rows, so if you're fine reusing row IDs then just don't specify it.

Tony Leung•3/31/24, 3:47 PM

hi guys, will there be a feature which allows foreign key check to be turned off while migrating database? I have an issue here: https://github.com/cloudflare/workers-sdk/issues/5438

GitHub

🚀 Feature Request: Allow turning off foreign key check while migrat...

Some table altering tasks in SQLite cannot be achieved without replacing it with a new table (by dropping - recreating the table) (like adding foreign keys, changing primary keys, updating column t...

IIsaac McFadyen AUTOINCREMENT literally just prevents reuse of row IDs from deleted rows, so if ...

Tony Leung•3/31/24, 3:52 PM

In my experience, having AUTOINCREMENT in database will make a huge performance impact on database cluster. Everytime I insert a new record, the database has to lock up the table and generate new ID for that record. I have to let it check across cluster or turn off cross-cluster check, which might cause an conflict. So unless that table don't have much activity and records are inserted in batches or you are not clustering/replicating the database, having a AUTOINCREMENT column in database is not a good idea. Use UUID or having a key generation service is better. I personally use ULID to allow time-based sorting on my database without indexing the created_atcreated_at column since most of tables are required to be sorted with created_atcreated_at descending.

LLarry What you are proposing is a sort of two-phase commit which would work but I don'...

John_rand•3/31/24, 4:56 PM

Thank you for your response.

Unfortunately, last_insert_rowid is not thread safe and should be used only in the same transaction. (Its local to the connection actually, but if the connection drops, you're left with tangling rows).
Having a temporary table is equivalent to having the same table with a flag (is_orphan) I think.

As for the guid, you're in the mercy of collisions, maybe equivalent to having a monotonically incremented separate table (sequence).

Unfortunately, it is indeed a 2-phase-commit problem, no solution feels right. Which is why posted the question on how people are handling it.

It is very unfortunate that D1 forces these problems on the consumer and that there is no clear guidance. Is it that much of a corner case wanting to insert an "order" with "order-lines" in a transactional manner?

JJohn_rand Thank you for your response. Unfortunately, last_insert_rowid is not thread saf...

Jason Hostetter•3/31/24, 5:07 PM

Aren’t batch inserts on D1 done in the same transaction? So you could use last_row_id safely? Generating your own uid seems like a good approach, are collisions a realistic problem for your application?

Original message was deleted

John_rand•3/31/24, 5:15 PM

Both correct. Needs very carefully crafted code on the client though. Not sure how I could do that with drizzle (call the function once, store it in a variable, have subsequent batches use that var)

On the collisions, it would affect my case yes, or at least it would help me sleep better at nights. ULID could be much easier option to adopt maybe - and drizzle friendly.

RexNormous•3/31/24, 10:18 PM

D1 updates incoming! https://github.com/cloudflare/cloudflare-docs/commit/0c71ecec03b2ac5e8103aa1e38f67a156ca26fe7

GitHub

[D1] fix some typos (#13367) · cloudflare/cloudflare-docs@0c71ece

d1: fix some typos
workers: Update betas.md
d1: Update pricing.md
d1: Update limits.md
d1: Update time-travel.md
d1: Update debug-d1.md
d1: Update backups.md

RRexNormous D1 updates incoming! https://github.com/cloudflare/cloudflare-docs/commit/0c71ec...

James•3/31/24, 10:26 PM

what do you mean? That PR is just fixing some typos! :Kappa:

James•3/31/24, 10:26 PM

Some super cool stuff tho, yeah

RexNormous•3/31/24, 10:26 PM

10gb max size db, 250gb total per paid account
and foreign key support too https://github.com/cloudflare/cloudflare-docs/pull/13708/files

Rafael França•3/31/24, 10:49 PM

Has anyone already tried to use a multitenant using multiple databases? How to solve the binding of each tenant?

KKai just noticed beta badge is gone, did d1 go GA?

isaiah•3/31/24, 11:32 PM

https://tenor.com/view/obi-wan-kenobi-these-are-not-the-droids-star-wars-jedi-mind-trick-gif-23067514

Tenor

isaiah•3/31/24, 11:32 PM

No, it has always been that way

JJames what do you mean? That PR is just fixing some typos! :Kappa:

isaiah•3/31/24, 11:35 PM

d1-beta channel to d1 channel when?

RRexNormous D1 updates incoming! https://github.com/cloudflare/cloudflare-docs/commit/0c71ec...

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

I'm waiting for them to let me run PRAGMA foreign_key=offPRAGMA foreign_key=off since the last time I update my table it was a nightmare

RRexNormous D1 updates incoming! https://github.com/cloudflare/cloudflare-docs/commit/0c71ec...

Kai•4/1/24, 7:29 AM

looks at current date hmmm

KKai *looks at current date* hmmm

Max (@rozenmd)•4/1/24, 8:41 AM

my favourite was this PR https://github.com/cloudflare/workers-sdk/pull/744

GitHub

Get out in front of trademark issues with `wrangler jeans` and `wra...

It's no secret that the wrangler 2 release is going to be big. Bigger than big. In fact, I don't think it's too much of a stretch to say it will change the way that software is develope...

RRexNormous 10gb max size db, 250gb total per paid account and foreign key support too https...

Matt Silverlock•4/1/24, 10:59 AM

D1 has always supported foreign keys: they are enabled by default. This is just documenting them so folks don’t have to dive into the (much denser) SQLite docs.

I have a question about dynamic bindings and the "Maximum bindings per Workers script" limit describ

Similar Threads

Similar Threads

Similar Threads