Requirements for an imperative language amenable to sql-like optimizations

> It starts by describing how sql can optimize “nested for loops”. Then it > breaks down (it “unexplains”) the common explanation: “sql can do that > because it is declarative”. Finally it provides 6 requirements for a language > to be able to implement this type of optimizations: If it's neste

Requirements for an imperative language amenable to sql-like optimizations

in SQLite, remove all but that one index and use [INDEXED BY](https://sqlite.org/lang_indexedby.html) ?

Requirements for an imperative language amenable to sql-like optimizations

By the way, I was thinking lately that I'd like a database engine where I could specifically tell how to fetch the data and what index to use, the compiler yelling at me if I try something impossible, rather than relying on declarative SQL, and depending on guesses from the query optimizer for p

Requirements for an imperative language amenable to sql-like optimizations

I have just read this very nice (deep and at the same time easy to ready and clearly written) article: It starts by describing how sql can optimize “nested for loops”. Then it breaks down (it “unexplains”) the common e

Requirements for an imperative language amenable to sql-like optimizations

What you say is true but very important lessons are missing here: ;-) 1. An imperative loop nesting structure can be optimized "by hand" and for quite some people the resulting system is more pleasant to work with than looking at strange graphs from a query optimizer trying to deduce where to