It will be cheaper? Damn.. how? If it will have the same eventual consistency characteristict I don'
It will be cheaper? Damn.. how? If it will have the same eventual consistency characteristict I don't see why would they make it cheaper
UWhile in public Alpha, D1 is currently free to use on all Workers plans. Refer to the our recent announcement) for more information.
VA lot more computes goes into serving a D1 request than just a KV get, or thats what it feels like anyways
UStorage is more expensive but reads/writes are cheaper but you have to use small values
Vat 2 MB / read they are the same price
V2MB is a lot.. 
U1MB is the max size of a value in D1
Uand do note that writes are significantly more expensive than that of reads... 1 million writes of 1MB is $1000
U5KB would cost the same as far as writes go but generally you probably wont go over 5KB that often for a normal DB usage 
Vso for large or somewhat large writes/reads KV is cheaper
Uyes
MThey won't have the same eventual consistency. KV is minimum of 60 seconds. Eventual consistency isn't the same across storage systems.
VBy that you mean that D1 aims for an even better consistency model? So like less than 60?
MYes, by far. Most databases replicate far more quickly than a minute.
VIs that because in the case of D1 replication means sending the list of changes to every replica and in the case of KV it could mean sending over 20MB of data?
UKV doesnt replicate data it uses a cache and the cache gets invalidated after a minute
https://developers.cloudflare.com/workers/learning/how-kv-works/#how-kv-works
https://developers.cloudflare.com/workers/learning/how-kv-works/#how-kv-works
Because Workers KV stores data centrally and uses pull-based replication to store data in cache...
SFYI there's a recent blog post about how the latest KV handles push vs pull : https://blog.cloudflare.com/faster-workers-kv-architecture/
II have seen this, too. I think it does the same thing even with .all(), though.
IYou can solve with the AS command, if you really need, but it’s a problem when you want to return everything
ILet me get home, it’s hard on mobile and I want to do that properly.
IIf I don’t reply in a couple hours ping me 
Vselect user.id as userid, data.id as dataid from user, databasially you just have to give a name for the keys which are the same
IThis is what I wanted to do, @yamiteru
M
Mwhich version of wrangler are you using?
Mpersonally:
Myou might need to follow these steps to remove v1: https://developers.cloudflare.com/workers/wrangler/migration/v1-to-v2/update-v1-to-v2/#1-uninstall-wrangler-v1
AIf you're on the old backend for D1, it should take backups every few hours automatically.
Afaik time travel for the new backend is planned but no release date is set.
Afaik time travel for the new backend is planned but no release date is set.
JD1 preparing for a world with fractional bytes! : )
MCan you show your queries? I would expect the index does not retain a reference.
II personally do these myself at the moment on the new backend.