Every so often the optimizer does it wrong. Instead of reading query plans [new language] and adding a layer of hints [yet another language], how about having a

Every so often the optimizer does it wrong. Instead of reading query plans [new language] and adding a layer of hints [yet another language], how about having a language that allows you to specify the precise order when you eventually care, and optimizes anyway by default. As opposed to three languages layered over each other in a fairly ad-hoc way. val q = Q.from(table).select(foo).filter(foo > 3) val q = Q.from(table).select(foo).filter(foo > 3).verbatim() PS. Also, the query plan language is now the same as the query specification language.