[truetraveller]

I'm not demanding. If "transparent" pricing is a key feature, then please at least provide detailed billing info/examples. From the billing page you linked, still have many questions: If I have a row that's 100mb, is that counted as one read? What about index creation, is that counted? Or, merging the WAL log with the base, is that free? And what is a read "unit"? is this different than a "row read".

[LewisJEllis]

Your comment used to read:

> C'mon guys, this is super basic.

which came off as demanding, until you edited it after my response to instead read "This is standard stuff".

It's bad form to make substantial edits an hour later after you've been replied to, especially if you then refute the reply based in part on that edit.

I agree with you that more examples would be helpful, and you have some good questions which are left unanswered, but "is it rows?" was answered very clearly by the pricing page and billing docs.

[truetraveller]

I edited it because I didn't want to be mean, and I thought that might have been mean. My intention was not to be less "demanding". In fact, I added to more questions to my list with my edit. So, I became even more demanding!

>"is it rows?" was answered very clearly

In the world of DBs, "rows" is extremely vague. We need more info, which is the point of my post.