> SQL is messy because describing the underlying data relationships are messy. Not sure that is true. You can imagine having a smaller query language with clea

> SQL is messy because describing the underlying data relationships are messy. Not sure that is true. You can imagine having a smaller query language with clean semantics able to capture messy data relationships. Small functional expression languages come to mind. Where it lies on the spectrum from purely-table-form to can-hold-everything is a design choice. Your query language doesn’t need to capture the underlying data model exactly. SQL is an example of this itself. I’ve run into the orthogonality issue myself several times. You don’t need to drop SQL today, but for some data domains more expressive query models can work really well.