I keep proposing Dynamic Relational (DR) be implemented, but the idea is dismissed for vague or inconsistent reasons. The "NoSql" movement has dynamic products,

I keep proposing Dynamic Relational (DR) be implemented, but the idea is dismissed for vague or inconsistent reasons. The "NoSql" movement has dynamic products, but they are too different from existing RDBMS. DR only tweaks what's needed to get dynamism, but otherwise sticks to most RDBMS and SQL conventions to shrink the learning curve for existing RDBMS shops. You can have your dynamic cake and RDBMS cake at the same time. To me it's a no-brainer. ( https://news.ycombinator.com/item?id=15352786 https://news.ycombinator.com/item?id=15352786 ) Note: JSON column types in existing RDBMS treat JSON-derived columns as second-class citizens. In DR all columns are equal citizens.