[gordaco]

Sorry if this comes out as a little irrelevant, but I'm so glad there is someone else out there who thinks like you. I' ve already given up on proselitizing about the advantages of good ol' relational databases at my office. We DO have a schema (which has been consistent from the start, i.e., we haven't used our database in a flexible way), even if it's not explicit, and enforcing it actively in our code is just going to result in more errors than letting any mature relational database do it. And, yes, we've had a few of those errors (of varying severity) that wouldn't have happened with a relational database.

Non-relational databases are good when the data is really mutable enough that each row may have fields of its own, or lack them. Maybe I'm naive, but I don't see it as that common, and it certainly isn't our case.