> So the database model and query language gets significantly more complex for dubious benefit. Sum types are definitively not a "dubious benefit". Neither ne

> So the database model and query language gets significantly more complex for dubious benefit. Sum types are definitively not a "dubious benefit". Neither nesting relations (that are not that different to join them and will provide better semantics that create a LOT of null columns to flat them). Will complicate matters and requiere extensions? Sure. But is clear that, today in this century, exist a lot of use-cases where people are resorting to pseudo-nosql (json embedding, to name one of the biggest anti-patterns), and that create more inconsistent features, extensions, weird extra syntax, etc. that anyway are required for it (and could have been cleaner under this idea). With this, we can get the same benefits and much more. P.D. Not against have a very simple core and try to model stuff that way, but the major point of a model, like relational, is support how to MODEL. And we need to model nested thing, and we need to model variants and get rids of nulls and all that. So, sometimes, you need to add complexity + 1 so you get complications - 10.