No and it should not be used for production
No and it should not be used for production
SThis is not working
SAny appropriate date when it will stable ?
W
WNo date outside of that
MWe don't give expectations or timelines for releases, but we'll announce it extremely loudly across the Internet when it's ready.
Mtbh I have a bunch of durable object code that I'm going to refactor to just use D1 once we go GA
Min other news, the D1 dashboard now lets you set fields to
null
MDepends what you mean by access D1 from the browser - like edit your data?
MOh, no you can't do that - your frontend has to talk to a Worker
Mbut like, your worker could just be a dumb pass-through for all queries from the frontend if you wanted to. i'm using that atm to build a REPL:
MJWT between your Worker and the frontend
MAt the moment (it's still in alpha after all) - it's just a single database on the edge
MWhen is d1 going GA
Mwhen it's ready
MLol any plans for it being ready soon?
Mwe'll announce it when it's ready
MI’m building a large project and getting to database design. I really want to use it but can’t wait too long
MSo I just wanted an idea if it’s going to be 1-3 months or 3-9
Mit's in alpha atm, and still needs a beta before GA
MWould it be a terrible choice to go with it in alpha if I’m growing really slowly?
MOr is alpha like not reliable
MAlso do you guys think d1 will get prisma support ?
Jif it's an important project, which "large project" sounds like, then no it's not a good choice.
In the meantime, I suggest you use another database service. For example I'm very excited about D1, but I'm watching my project with planetscale. I'll migrate as soon as I can.
Cloudflare will never give a release date for any product or fix or service. The canned response is always .
In the meantime, I suggest you use another database service. For example I'm very excited about D1, but I'm watching my project with planetscale. I'll migrate as soon as I can.
Cloudflare will never give a release date for any product or fix or service. The canned response is always
.
MOkay. Thank you. Would a specific database be similar enough where transition later can be much easier? Would planet scale be the next best option?
JI didn't put a lot of effort into research. I just knew that planetscale would meet my needs and had a serverless driver.
you might also want to check out:
• Turso https://chiselstrike.com
• xata.io
you might also want to check out:
• Turso https://chiselstrike.com
• xata.io
Eliminate application bottlenecks by bringing the performance and data portability of open source, lightweight SQL close to your users with low overhead
SThis is working good
M@elithrar ^
MWe’ll be announcing (just announcing: not enabling) pricing in a few weeks, but it’s very much an “it depends” case. DO is key-value based, whereas D1 is a queryable database. If you have a lot of small reads, then D1 is likely to be much cheaper. DO charges on 4KB boundaries. I’d need to know a LOT more about your query patterns here.
MWhat are the limits of d1
MLike as far as how much data it can store
M(Remembering that D1 is an alpha: a true alpha, not a marketing alpha!) 
MSo if d1 is 100mb limit I’m trying to understand how that can be useful? Like say I’m storing e-commerce orders. What do we do when we reach a limit
