Thank you. I wasn't aware of that. Yeah, there are three things in play (I would say): 1. The language design of SQL is often icky. A different logical lan

Thank you. I wasn't aware of that. Yeah, there are three things in play (I would say): 1. The language design of SQL is often icky. A different logical language could be nice. 2. The logical / physical separation is sometimes right on and sometimes... not so much. At the very least, there doesn't seem to be One True Logical Model, hence exposing a physical model with transactions seems justified. 3. Often, people are quick to give up consistency and while that is not always the wrong thing to do, it's done more than it ought to be. But... a lot of people hacking up big sites and similar these days... their standards are low and the "customer's" tolerance for resulting bugs and glitches is startlingly high (for now). All three of those get lumped under the "NoSQL" heading and it is helpful (I think) to tease them apart.