Are you able to request a limit beyond that or is it still a hard-coded value like in the beta?
Are you able to request a limit beyond that or is it still a hard-coded value like in the beta?
MWe 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)
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)
MKeep in mind that a 10GB database storing user records @ 1KB per row = 10M users.
VThat'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
Tdoes SQLite View improve query speed? I'm not planning to join view with anything else
RSame here. I tried specify a region and it works.
M@geelen
MAre you still seeing this? I was able to create a new DB just now.
MOK, looking into it. My new DB was automatic (based on your previous comment).
THi 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.
TA sample scenario was mentioned in this issue https://github.com/cloudflare/workers-sdk/issues/5438
GitHub
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...
Vcheckout https://developers.cloudflare.com/d1/build-with-d1/foreign-keys/#defer-foreign-key-constraints
Cloudflare Docs
D1 supports defining and enforcing foreign key constraints across tables in a database.
TThis 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
VGot 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.
KCorrect
TYeah 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.
TMy 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
VThank you!
MThe 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
MCan you try one more time when you're back online?
SIs it possible to share a d1 database between worker and pages locally?
SI'm symlinking the wrangler folder, it seems to work but was curious if there is a better way
Mwe are working on making it faster tho
CI 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?
CYes, but how can I know that the read replicas are caught up at that point
CCloudflare Docs
Create, develop, and deploy your Cloudflare Workers with Wrangler commands.
CLooks 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
Now the question is, when will we get the D1 Location Hint for Oceania? ;p
Where Durable Objects Live
Tracking where Durable Objects are created, wherever you are in the world.
C(I tried using the api and not the dash with
oc and it still rejects it lol)CThere is now, it was just released?
LDoes anyone have a comparison of D1 vs Turso?
Lit's an upcoming feature which breaks compatibility with previous API
ZIt 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
LSo you can use both at the same time? Just one will make use of the deployed replicas while the other won't?
ZI 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.
UIf theres any changes it will be guarded by a compat date/flag
AHey team, What is the best implementation to achieve realtime using d1? some sort of CDC or access to the WAL?
MExactly this.
You can use the existing
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.
You can use the existing
env.DB.prepare() and other APIs, or you create a session via let session = env.DB.withSession(commitToken) and then call session.prepare(), 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.
FDo we really need replicas if we go 1db/user 
if we dont have heavy writes ofc
if we dont have heavy writes ofcUreplicas only helps with reads not writes
Jare there any tools that let you explore your d1 database with a gui similar to drizzle studio?
Jgoing to have a play with d1-manager, curious to hear if anyone's had any experience with it or has any other suggestions
