Damn, I'm not even able to return a single column now :( `SELECT date FROM outputs`
Damn, I'm not even able to return a single column now :(
SELECT date FROM outputs
MDid the sensible thing and stopped relying on the bigger endpoints and instead created a few more specialized ones
UThere will be some limit which right now is on the lower end but they are working on increasing it... which I assume the new backend has increased that a good amount given what I read from the blog
IDO has somewhat different goals than D1 so I expect they will continue to exist.
IDO = global "actor" model, there will always be one unique actor per ID/name in the world, that actor has access to key-value state
D1 = a "database", with tables/rows/columns etc.
D1 = a "database", with tables/rows/columns etc.
UIts friday night and this is an alpha product so I doubt anything will be done until monday when they are back at work.
MTechnically, Wrangler calls the new D1 a Beta
M
HThat isn’t the right type for a D1 DB stub(let me check for it). Bindings usually can’t be logged to the console. And to check, have you added the D1 binding to the Cloudflare Dashboard? Pages doesn’t respect
wrangler.tomlThe type is
D1Database
II'm uncertain whether you can force reads to go to the primary (well replicas aren't even out yet haha) but that would be cool.
IOh cool, that will be good then.
UDOs can act like KV as well if you just add cache in front of it 
UThis is how I decide:
large blobs?: R2
key value?: DOs
SQL?: D1
KV: almost never
large blobs?: R2
key value?: DOs
SQL?: D1
KV: almost never
HKV: Large-Scale Key-Value(100+ rps)
HEspecially if requests come from different colos
UI would still use DOs for 100+ rps just with cache in front. Pretty much the only case I would use KV atm is a session store instead of creating a DO and using cache for that
JKV is fantastic and I would always recommend it for read-heavy operations. If you need global durability then of course DOs and things like that are gonna be better, but if you don't (like so many use-cases), KV's simplicity and pricing is incredible.
Jyep
HDepends. The DO could be in the same colo, and then you probably won’t get much, if any, difference
HAnd that all depends on caching, which you can do against a DO too
HTL;DR, KV and DOs are two pretty different products, and thus neither is a one size fits all solution. Use your own judgements, and try to run the math yourself if you want
IAre you using the new backend?
BI noticed is that it is throwing CORS issue when I sent in fetch body, a text when database schema is expecting number like ' phone:"abc" ' instead of 'phone:123' , which should as per me should be database error, not cors error. Is it common ?