> I agree with you example, in that case it is useful. It's just that it is a pain in the ass in so many other cases. It's a pain, because what we really want

> I agree with you example, in that case it is useful. It's just that it is a pain in the ass in so many other cases. It's a pain, because what we really want in such cases is a datatype server, not a relational database. For all of SQL's merits, the NoSQL backlash was not without cause. For too long the SQL hammer has been wielded to pound in too many screws. Of course, programmers being programmers, NoSQL turned into just another hammer used in just as many inappropriate situations. The example I outlined is not a theoretical one. I've dealt with such situations...but I've done so with Datomic, which is designed with datatype-composability in mind. Similarly, I've found a healthy mix of SQL, Redis, memcache, and Datomic all in moderation can go a long way. ...but I've still not found a solution where Mongo is the obvious answer.