Earlier quoted context omitted.
tz setup is done with executing a single script. not surprising they could fix quickly. bigger surprise is they forgot to do this before youre support request. generally this is table stakes for managed DB this is fourth day in a row of planetscale ads^H^H^H blog posts being on hn front page. as i mentioned on yesterdays thread, innodb_rows_read is known to be buggy. regardless, by design it includes cached rows. ter…
"real cloud providers" most definitely charge based on rows read/written. Many startups / side projects choose the on-demand billing model because they don't want a fixed $x / mo when they don't need it. Some of them also have pre-provisioned options, and it seems likely that Planetscale will probably end up doing something similar. https://aws.amazon.com/dynamodb/pricing/ https://firebase.google.com/docs/firestore/p…
your first two examples are nosql. third example charges by data size processed, not by rows!
rows is weird metric since some tables have tiny rows, some have huge