we're very aware 100MB is limiting - looking at higher limits for beta
we're very aware 100MB is limiting - looking at higher limits for beta
Mdoes it work without the numbered params? as in just
?think there's a bug in miniflare
NYes, sorry, I'm aware that you're aware. My question is whether it will change to not load the entire db into ram, so that large dbs could be possible and affordable? If so, I'm happy to work within the alpha and beta limits. But otherwise, there's no point in me dedicating time to this if it won't be possible/affordable to use D1 in production
Mnot sure yet tbh, next goal is at least a gig
NOk. I suppose I'll just keep an eye on this then. What I'm curious about is not what the limit will evolve to be, but whether it will be tied to ram (expensive and size-limited) vs ssd (cheap and unlimited in size). If there aren't currently any plans to consider moving out of ram, I can't justify testing D1
NI'm sure it'll be a wonderful solution though for many smaller applications!
Myes please
Mfor my own projects I'm thinking of an architecture where I use a d1 db to track which d1 db contains which customer's data
Mas CF raises limits it'll make it more and more viable (imo)
NI don't think that would work for my architecture/application. And, again, my issue is with it being stored in expensive ram - even if the architecture was split like you suggest, it would still be orders of magnitude more expensive than ssd.
MCC : @geelen if you have thoughts
M(fwiw I'm more involved in building the developer experience, like wrangler commands and dashboard UI, so I don't have deep insights here)
AHello, does D1 have an UI like PHPMyAdmin or Adminer ?
Mjust the cloudflare dashboard for now, but I'm going to build one you can download/deploy
MGitHub
D1 Manager is a web UI and API for Cloudflare D1, a serverless SQL database. It provides a user-friendly interface for managing databases, tables, and records, as well as an API for performing oper...
AI just tested it, it sort of works, but is very primitive
Can't edit a table, and some types are missing, but I do understand that it's a beta
Can't edit a table, and some types are missing, but I do understand that it's a beta
AAs long as the one you build is feature rich and lets us do a lot of operation, I think it's gonna be great
Mraise a ticket anyway, it helps
Mnot that I'm aware of
Mwe are exploring using Workers that deeply integrate with D1 as an extension alternative, though
SSo in a real project, with d1 as database. Having a d1 database for a customer is better than a large d1 database for all customers?
SI don’t know the infra under the hood. But I would prefer sharding because the natural of workers
SI think it depends on how data is organized. Sharding won’t work well for all database. My idea was because of the natural of worker. Sharding won’t be a problem if it suits
HIs sharding separate from the read-only clones idea from a while ago?
