This is already the case. Nowadays, almost all relational databases (except, of course, MySQL) support XML columns. PostgreSQL supports them rudimentary, and DB2 and MSSQL have even special storage strategies and index structures for XML, i.e. for generic tree structures, data-oriented as well as document-oriented ones.
Also, abstract data types ("encapsulation", the base of OO) are implemented in these databases, too (except, of course, in MySQL), as well as other OO features such as table inheritation and some kinds of polymorphism.
Having XML or JSON columns that can their interior fields indexed, would replicate what document databases do.
Also what having a master-master relational database with a bunch of materialized views replicate what people are using Cassandra for. Is it just because the free databases don't have materialized view support?
* have individual tables, indeces and views that are either relational or document-oriented, or graph- or object-based while we're at it, on a case-by-case basis,
* manage them all in a single, well-known distributed pool,
* and present a unified API to access all of them (e.g. a Structured Query Language of some sort)
* that allows tables of disjoint types to be joined in queries, with appropriate warnings when it creates non-optimized query plans?
In other words, why can't I say that my reports table should use the "relation" backend, while my messages table should use the "document" backend, and be done with it?
It's as if, when you went to a car dealership, they asked you whether you wanted to see the "cars with cigarette lighters" or "cars with automatic windows" section. Why can't my car do both?