Are you able to use the limit request form to get increased per database now? I’m happy with no repl

Are you able to use the limit request form to get increased per database now? I’m happy with no replicas as a tradeoff, just want to be future proof with more storage.

VVillage (Josef)Are you able to use the limit request form to get increased per database now? I’...

Matt Silverlock•4/3/24, 2:19 AM

All existing databases (if you have a paid Workers plan) can grow to 10GB each - https://developers.cloudflare.com/d1/platform/changelog/#d1-is-generally-available

Cloudflare Docs

Changelog · Cloudflare D1 docs

D1 is now generally available and production ready. Read the blog post for more details on new features in GA and to learn more about the upcoming D1 …

MMatt Silverlock All existing databases (if you have a paid Workers plan) can grow to 10GB each -...

Village (Josef)OP•4/3/24, 2:20 AM

Are you able to request a limit beyond that or is it still a hard-coded value like in the beta?

VVillage (Josef)Are you able to request a limit beyond that or is it still a hard-coded value li...

Matt Silverlock•4/3/24, 2:22 AM

We don’t currently increase that limit - it’s not that it’s hard coded, it’s that we have a very (very) high bar for performance & cold starts.

We’re continuing to work on raising it over time - and as we do it’ll just work. But also unlikely a single D1 DB will be 100GB (which is a large transactional DB by any standard)

Matt Silverlock•4/3/24, 2:23 AM

Keep in mind that a 10GB database storing user records @ 1KB per row = 10M users.

Village (Josef)OP•4/3/24, 2:24 AM

That's fair yeah, we're considering a serverless migration at work and our current DB is 108GB (we can't split by user with our use case) so size is the issue

Tony Leung•4/3/24, 4:36 AM

does SQLite View improve query speed? I'm not planning to join view with anything else

Original message was deleted

Ray Hao•4/3/24, 10:51 AM

Same here. I tried specify a region and it works.

Original message was deleted

Matt Silverlock•4/3/24, 11:18 AM

@geelen

Original message was deleted

Matt Silverlock•4/3/24, 11:21 AM

Are you still seeing this? I was able to create a new DB just now.

Original message was deleted

Matt Silverlock•4/3/24, 12:28 PM

OK, looking into it. My new DB was automatic (based on your previous comment).

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

Hi guys, is there anyway to turn off foreign key check while migrating the database? Some table altering tasks needs table to be dropped, which will cascade referenced tables.

Tony Leung•4/3/24, 1:39 PM

A sample scenario was mentioned in this issue 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...

TTony Leung Hi guys, is there anyway to turn off foreign key check while migrating the datab...

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

checkout https://developers.cloudflare.com/d1/build-with-d1/foreign-keys/#defer-foreign-key-constraints

Cloudflare Docs

Define foreign keys · Cloudflare D1 docs

D1 supports defining and enforcing foreign key constraints across tables in a database.

VVy checkout https://developers.cloudflare.com/d1/build-with-d1/foreign-keys/#defer-...

Tony Leung•4/3/24, 1:46 PM

This works with table creating or importing but not for table dropping. Matt also suggested me to bracketing the migration by that pragma but sadly it didn't work

Village (Josef)OP•4/3/24, 2:23 PM

Got another question, there's still no way to dynamically bind to databases correct? I.e. bind to all 50k DBs from a Worker instead of the ~5k that'll fit in wrangler.toml? I believe you can use the API, but that kind of defeats the purpose.

kian•4/3/24, 2:25 PM

Correct

Original message was deleted

Tony Leung•4/3/24, 2:26 PM

Yeah I think it's the only way to add foreign key or change column type, but whenever I drop the table, all records in tables which reference to the table dropped before are gone too because of cascading on delete.

Tony Leung•4/3/24, 2:30 PM

My current approach is store the child table data to a temp table then insert it again after migrating the parent table. But when my child table also has some more children, the task turns out to be complex and wasteful

Kkian Correct

Village (Josef)OP•4/3/24, 3:10 PM

Thank you!

PPelps Hi. Is there any work on a package similar to database-js from planetscale to al...

Max (@rozenmd)•4/3/24, 5:03 PM

The REST API is significantly slower than a Worker, would recommend a simple wrapper over a Worker instead: https://github.com/elithrar/http-api-d1-example

Original message was deleted

Max (@rozenmd)•4/3/24, 5:07 PM

Can you try one more time when you're back online?

squareclamp•4/3/24, 5:24 PM

Is it possible to share a d1 database between worker and pages locally?

squareclamp•4/3/24, 5:31 PM

I'm symlinking the wrangler folder, it seems to work but was curious if there is a better way

PPelps I mostly use workers. I was just curious cause some ppl might like D1's offering...

Max (@rozenmd)•4/3/24, 6:16 PM

we are working on making it faster tho

Cory•4/3/24, 6:48 PM

I am trying to understand how session-based consistency would work in an application such as SvelteKit and the data invalidation methods. I understand the example of consistency when executing multiple queries in the same function, but how can I guarantee that the next reload of the page will be up to date? Does anyone have any examples of this?

Original message was deleted

Cory•4/3/24, 8:03 PM

Yes, but how can I know that the read replicas are caught up at that point

Ggotfredsen but .. where is the D1 download .. / export .. for backup ? 🙂

Cyb3r-Jak3•4/3/24, 8:19 PM

https://developers.cloudflare.com/workers/wrangler/commands/#export

Cloudflare Docs

Commands - Wrangler · Cloudflare Workers docs

Create, develop, and deploy your Cloudflare Workers with Wrangler commands.

Chaika•4/3/24, 9:00 PM

Looks like Oceania/Australia DOs are online! https://where.durableobjects.live/colo/SYD/
Now the question is, when will we get the D1 Location Hint for Oceania? ;p

Where Durable Objects Live

Sydney, New South Wales, Australia(colo) | Where Durable Objects Live

Tracking where Durable Objects are created, wherever you are in the world.

Chaika•4/3/24, 9:00 PM

(I tried using the api and not the dash with

oc

oc

and it still rejects it lol)

Original message was deleted

Cory•4/3/24, 9:07 PM

There is now, it was just released?

LordSilver•4/3/24, 9:07 PM

Does anyone have a comparison of D1 vs Turso?

LordSilver•4/3/24, 9:13 PM

it's an upcoming feature which breaks compatibility with previous API

LLordSilver it's an upcoming feature which breaks compatibility with previous API

zegevlier•4/3/24, 9:15 PM

It doesn't break compatibility with the old API, you can still use the old API just fine. It's just that there is no change to behaviour of the "old" API when the new API is introduced

Zzegevlier It doesn't break compatibility with the old API, you can still use the old API j...

LordSilver•4/3/24, 9:16 PM

So you can use both at the same time? Just one will make use of the deployed replicas while the other won't?

LLordSilver So you can use both at the same time? Just one will make use of the deployed rep...

zegevlier•4/3/24, 9:18 PM

I can't confirm whether you'll be able to use them simultaneously, but D1 is a GA product, so I would not expect any of the current APIs to change in a backwards-incompatible way.

Unsmart•4/3/24, 9:20 PM

If theres any changes it will be guarded by a compat date/flag

albyzyx•4/3/24, 9:55 PM

Hey team, What is the best implementation to achieve realtime using d1? some sort of CDC or access to the WAL?

Zzegevlier It doesn't break compatibility with the old API, you can still use the old API j...

Matt Silverlock•4/3/24, 9:58 PM

Exactly this.

You can use the existing

env.DB.prepare()

env.DB.prepare()

and other APIs, or you create a session via

let session = env.DB.withSession(commitToken)

let session = env.DB.withSession(commitToken)

and then call

session.prepare()

session.prepare()

session.batch()

session.batch()

, etc, etc.

We aren't breaking the APIs. Users that never adopt the session API will have D1 as it works today, with the same consistency model they've built their app against.

Developers who want to use replicas can adopt the session API.

forslunds•4/3/24, 10:02 PM

Do we really need replicas if we go 1db/user

if we dont have heavy writes ofc

Unsmart•4/3/24, 10:05 PM

replicas only helps with reads not writes

Are you able to use the limit request form to get increased per database now? I’m happy with no repl

Similar Threads

Similar Threads

Similar Threads