in a single worker.. not a single pages function? 🥲
in a single worker.. not a single pages function? 
HAll of the Functions in a Pages Project are bundled into a Worker, so it should apply to Functions too
Fif i got a cent for every time i heard that.. 
Mthis, but I always worked around Pages functions not having all the features by using a separate Worker for my API
Workers and Pages becoming the same "thing" will make this better
Workers and Pages becoming the same "thing" will make this better
BIf your service gets to that size then you shouldn't be using sqlite (which is what D1 is) anyway.
I have one app with 8000+ users and over 11 million records in the db and it is under 2gb, so I dont think it's an issue unless you are storing some big data in there
I have one app with 8000+ users and over 11 million records in the db and it is under 2gb, so I dont think it's an issue unless you are storing some big data in there
GIs there a max db count limit?
BIt's 50,000 but they've mentioned they've just set that so people don't go crazy. It can be increased to anything.
https://developers.cloudflare.com/d1/platform/limits/
https://developers.cloudflare.com/d1/platform/limits/
Cloudflare Docs
If you would like to explore other storage solutions for your application, Cloudflare also offers Workers KV, Durable Objects, and R2.
GOh jesus, sorry, I'm blind, it's the top line 
Mwhen we release dynamic bindings, it'll look a bit more like DO's limits page
BNext we need an unlimited KV's limit That one is pretty small
That one is pretty smallGThere is a "Limit Increase Request Form" for KV
https://developers.cloudflare.com/kv/platform/limits/
https://developers.cloudflare.com/kv/platform/limits/
Cloudflare Docs
Request adjustments to limits that conflict with your project goals by contacting Cloudflare. To request an increase to a limit, complete the Limit …
HYou can also just create new “namespaces” by giving each a prefix
BYeah this is a thing, but that workaround wouldn't be good in combination with Workers for Platforms, otherwise the user workers will be able to see other's data
BI've never tried the limit increase before but I've seen some people here mention their requests went unanswered for weeks so it puts me off a bit (and it is strange hosting it on a Google form, doesn't feel official)
MMMfigure out how big your rows are, divide 10GB by that size, that's how many rows you can store
Mthe classic challenge is figuring out the right way to split the data, not always easy
Mnot without polling the db, not yet anyway
Msay you have a blog with 10kb of text (~1k words) per article, that's a million articles for 10GB
Mthis doc might be useful https://developers.cloudflare.com/d1/build-with-d1/query-json/
HCould you pass in an RPC target that makes reads only to their “namespace”?
Mwouldn't you want to do something like:
json_extract(titles, $.romanji) as romanji, json_extract(titles, $.english) as english, ...not sure if sqlite supports the idea of nesting objects in a response
Mtitles -> $titles ->> $
Dis it safe to leak the database id? i.e. to publish
wrangler.toml
HYes. The entirety of
wrangler.toml
AThe ID only works for workers in your account so it should be fine
