We’ll manage that behind the scenes so you can read your writes. When we ship replication there will
We’ll manage that behind the scenes so you can read your writes. When we ship replication there will be docs covering all of this 
MLooking. Is this still occurring?
CThanks! Yea it seems to be in an even worse state now, it's not instantly erroring, but infinitely loading, queries against it, and trying to load it in the dashboard, just take so long I get a gateway timeout
Edit: Looks like I'm back to instant d1 errors, same error as above. Still broken sadly
Edit: Looks like I'm back to instant d1 errors, same error as above. Still broken sadly
MOkay thanks 
MStill broken?
Ahey guys, can we manage the database using some client?
MThe Drizzle team are working on support in Drizzle Studio - https://twitter.com/drizzleorm/status/1675617777636212738?s=46
Drizzle ORM (@DrizzleOrm)
Twitter
•
We will make @Cloudflare D1 adapter this week for Drizzle Studio, should be great
Likes
105
7/2/23, 9:29 PM
AI'll dump it and upload it
Cit is yea
972558fd-cadf-4bec-8b0b-5a140d7d51fb
972558fd-cadf-4bec-8b0b-5a140d7d51fb
C@elithrar can I jump on this thread or should I open a new one? I'm getting an error when trying out your tutorial.
MThis is definitely not related to Chaika’s issue. I think you have a typo in your code (unexpected token).
CIt wasn't immediately clear to me that this is a subchannel for all things related to d1-open-alpha -- sometimes I overlook the obvious.
CBut the error I got, if it's a typo, I'm pretty sure I copied and pasted from the example you give on Github.
MWhich example? Mind stepping back a sec and helping me understand a) what you’re trying to run / b) the code?
CThanks, I'm trying to run the https://github.com/elithrar/svelte-demo-d1 and I put the sample code in src/routes/api/users/+server.js -- (the only difference I see is that I'm using .js and not .ts)
GitHub
Cloudflare Pages + SvelteKit + Cloudflare D1 - https://developers.cloudflare.com/pages/framework-guides/deploy-a-svelte-site/#deploy-with-cloudflare-pages
- GitHub - elithrar/svelte-demo-d1: Cloudf...
MIf you aren’t building TypeScript I can’t guarantee it will work. That is also my personal account - not an officially supported project. I strongly recommend using our official tutorial first: https://developers.cloudflare.com/pages/framework-guides/deploy-a-svelte-site/#deploy-with-cloudflare-pages
Svelte is an increasingly popular, open-source framework for building user interfaces and web applications. Unlike most frameworks, Svelte is …
MI have that exact repo deployed as a project: if you're changing things it's probably breaking it.
CI have deployed several sites already, following both the Cloudflare tutorial and Sveltekit's guide. Functions are proving a challenge.
MMIf 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"I'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 resetWe'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