If this is specific to Pages Functions, I'd ask over in #pages-help
If this is specific to Pages Functions, I'd ask over in #pages-help
CI have started reaching out there, too.
MI just forced a rebuild of that Pages site — unchanged, not a line changed from my original push ~3 weeks ago — and it works: https://32b48f37.svelte-demo-d1.pages.dev/api/users latest deploy, just pushed ~10 seconds ago.
I would ask in #pages-help and be very clear about what you're changing here.
I would ask in #pages-help and be very clear about what you're changing here.
CI'll keep at it. What does your users database look like, do you have the schema?
CI see it from the output, email, id, etc. but I haven't actually added any tables to the db. I was hoping it would just return some system info to start. Maybe the error has to do with an incomplete db setup.
MIt's impossible to tell from the error you've posted. If you haven't populated your DB - it won't work.
The query in the example app is just
The query in the example app is just
"SELECT * FROM users LIMIT 5" — it doesn't matter what the schema is because the query doesn't do anything smart.MI'm off for the night, but I'd strongly recommend:
- Going through the D1 tutorial first if you haven't. If you're also new to SvelteKit, then you're just adding friction: https://developers.cloudflare.com/d1/get-started/
- Once you have that working, deploy a basic Svelte site to Pages: https://developers.cloudflare.com/pages/framework-guides/deploy-a-svelte-site/
- Then you can combine it all
COkay, thanks for your help!
CFIY -- https://temp-d1demo-ts.pages.dev/api/users it's working for me. I made a fresh repo with JSDoc and it didn't work. Then I made a fresh repo and created the sveltekit app with TypeScript and it worked. Thanks so much for this. It's really interesting to get this all combined and working.
VHow many regions will D1 replicate to? Regional level?
Vany predictions? i'm evaluating using D1 or Dynamo and if the replication is similar to like a 3-4 region deployment with a singler writer and N read replicas I might aswell just stick with Dynamo
VThey surely wont put replicas in every PoP
MKeep in mind that each Dynamo replica adds to your storage costs + adds additional replication costs. D1 will not for the 'default' global replication.
M(I like a lot of what Dynamo did, but replication stacks up fast: https://aws.amazon.com/dynamodb/pricing/on-demand/)
Mhttps://silverlock-d1-remix-svelte-e.cloudflare-docs-7ou.pages.dev/d1/examples/
- what framework should we add next? The Pages docs cover the whole list, but (IMO) having specific examples you can copy+paste to get started for D1 == easier
UI assume D1 will only be single region writer? Or will it be like Dynamo where you can write to the primary node in each region?
MSingle writer: we think (and others like PlanetScale & Google's Spanner team also share this view) that multiple writers introduces too many consistency issues for user-facing apps. DynamoDB makes a bunch of trade-offs (and they are welcome to!) that we don't think are the right ones for user-facing apps / cause you to have to think about consistency a lot in your app design.
VNext.js definitely
M
GitHub
Type-Safe, Full-Stack Starter Kit for React Native + Web. - GitHub - timothymiller/t4-app: Type-Safe, Full-Stack Starter Kit for React Native + Web.
VIn terms of scale do you think you will have an upper cap or it's planned to support even terrabytes in db size?
MI don't think single databases with terabytes of storage are likely, but I also don't think they make sense elsewhere. A Postgres database or MySQL database with > 100GB will start to see scaling and query performance issues. If you need a single DB with terabytes of storage there's likely an application architecture issue.
CColin
CSorry if this has been asked before.. I am new to a discord and to cloudflare. The documentation says it is not stable and thus@not ready for production. What other options are available for a cloudflare-distributed web-app that requires a basic database?
Jfrom the looks of things, that repo only interacts with D1 in a worker script, not Next.js, so I would probably avoid using that as an example for Next.js personally
Mhttps://developers.cloudflare.com/pages/framework-guides/deploy-a-nextjs-site/#use-bindings-in-your-nextjs-application is the generic example, that applies to KV/R2/D1
MThis isn't to say we won't add a pointed D1 example, but there is a Next.js example
JI know - I was the one who updated that 
I'm just saying that the example you linked to the person who said Next.js doesn't actually use it in Next.js
I'm just saying that the example you linked to the person who said Next.js doesn't actually use it in Next.js
CDid you ever get a chance to check into the broken d1 db 972558fd-cadf-4bec-8b0b-5a140d7d51fb? I don't mean to bother you, not critical, I'm duplicating all my writes/etc to Planetscale for this purpose, but it's still dead as a doornail, seems to go between the states of being completely dead/unreachable (Gateway timeouts) and instant d1 errors
D1_ERROR: Error: Internal error while starting up D1 storage caused object to be reset, weird to me since it's just all of a sudden it died, I'm doing a lot of batched writes/updates to it, maybe maxed out some invisible limit, it's on the experimental backend
MWe're still looking: you've hit what looks like a very rare edge case. Been debugging it since yesterday — we need to cut a release to get more info from the writer flow. Will let you know once we see it fixed
CThanks! Just my luck lol, I suppose it's good to hit these errors now rather then later though
HI’m wondering, for large applications with data in the TB range, would sharding work? And if so, would there be a way to shard natively with D1, or is that something we need to handle ourselves?
MThis is definitely something we're thinking about. Being able to shard across multiple DBs based on some form of
shardKey (and how to make that easy for users).MAt the same time, if you have a single DB in the TB range... there are many, many other considerations. You're probably running more OLAP type workloads, storing large blobs, etc.
Abefore we start getting charged, will we be able to see metrics for read/write units used?
Anice. Any idea when thats happening? or just some time before pricing starts
Aok, thank you
VWhat's the best way to cache responses from D1? The Cache API?
It seems kinda sub-par, since AFAIK it only caches in the a local PoP. It would be nice to go at least regional
It seems kinda sub-par, since AFAIK it only caches in the a local PoP. It would be nice to go at least regional
VKV is the best option in the cloudflare arsenal for it?
Muntil we start handling the regional read replicas for you, probably yeah
Mcan do
MGitHub
Which Cloudflare product(s) does this pertain to? D1 What version of Wrangler are you using? 2.19.0 What operating system are you using? macOS Describe the Bug As per issue #555 we can see, that d1...
Mwe need it 
CIf the issue is still open then I would assume it hasn't been fixed
Mjust a kind reminder
CAny timetable on when the 1GB storage will be available?
A+1 I'm also keen for this to be fixed. It has flow on effects in drizzle-orm, joins just don't work correctly for any queries run against D1.
MI can send you a temporary fix if you are stuck with it
ANah that's ok, I've worked around it by not using joins for now. But it's definitely something I have to actively work around, so keen for a fix from the Cloudflare team.
