3 ms·
this is exactly why i built Rad: a relational db with an IR as its public interface, so you can experiment with interesting query languages against a solid foun
by Southclaws 1mo ago
this is exactly why i built Rad: a relational db with an IR as its public interface, so you can experiment with interesting query languages against a solid foundation and a real planner without needing to compile-up to sql (radengine.dev)
- crabmusket 1mo agoOh this is awesome. This is exactly what I've been too lazy to build for years now. We don't need a new syntax. SQL, PRQL or whatever else should compile down to the database's machine readable interface, same as language-integrated query builders or libraries like your generated clients. Did you come across Substrait when working on this? Any thoughts? This also sounds like what Turso imagine doing with their VDBE: > Like SQLite, it compiles SQL into bytecode for that machine, the VDBE, and then runs the bytecode. That design is what lets one engine host more than one SQL dialect. SQLite is the first and primary frontend that compiles to it, and Postgres is now a frontend of its own, with its own dialect and wire protocol. More will follow. Our goal is to be for databases what LLVM is to compilers, with one modern and reliable core, and many frontends compiled down onto it.