3 ms·

My dream would be a database where Haskell is the query language. It's more expressive than SQL and more composable. Every time I see a new SQL feature that wou

My dream would be a database where Haskell is the query language. It's more expressive than SQL and more composable. Every time I see a new SQL feature that would be trivial in a modern language it feels like we're working harder instead of smarter.

refset 2y ago
In case you weren't aware of TutorialD / Project:M36 already: https://github.com/agentm/project-m36 https://github.com/agentm/project-m36 > Unlike most database management systems (DBMS), Project:M36 is opinionated software which adheres strictly to the mathematics of the relational algebra. The purpose of this adherence is to prove that software which implements mathematically-sound design principles reaps benefits in the form of code clarity, consistency, performance, and future-proofing. > Project:M36 can be used as an in-process or remote DBMS. > Project:M36 is written entirely in the Haskell programming language.
ThinkBeat 2y ago
On Microsoft SQL Server you can use native .Net to write stored procedures and functions.
kthielen 2y ago
I made something like this for Morgan Stanley some years ago, a structurally typed eager variant of Haskell with static elimination of type class constraints (so no runtime penalty for overloading) and uses LLVM for the back-end: http://github.com/morgan-stanley/hobbes/ http://github.com/morgan-stanley/hobbes/ We used it for processing and analyzing billions of events per day. Using structural algebraic types let us encode market data (obviously) but also complex data structures inside trading systems that we could correlate with market data. As you say, Haskell-ish expressions are much more compact and capable than SQL, which was one of the reasons I wanted to build it. It also had a somewhat novel compression method (“types as probabilities” if you like the old Curry-Howard view), which was very important to manage billions of daily events. Good times.
whateveracct 2y ago
Sooooo if you use a SQL database and a Haskell access library, you kind of get this. Like esqueleto for instance. With it, you basically use Haskell as a meta-programming language for SQL. It's really nice when it works. But yeah..makes me think that a more first-class thing would be even better. Tbh, maybe Haskell compiled to a lower-level query language would be better. A language that is about tables and btrees etc. Where there's no planner because the low-level language is the plan.
- lmz 2y ago
  Most planners use statistics. A fixed plan may not be optimal (and at the same time, statistics may be out of date).
tehlike 2y ago
As far as query languages go, you may want to look into prql, kusto or google's alternative (i forgot its name). They are composable, and more natural.

refset 2y ago

In case you weren't aware of TutorialD / Project:M36 already: https://github.com/agentm/project-m36 https://github.com/agentm/project-m36 > Unlike most database management systems (DBMS), Project:M36 is opinionated software which adheres strictly to the mathematics of the relational algebra. The purpose of this adherence is to prove that software which implements mathematically-sound design principles reaps benefits in the form of code clarity, consistency, performance, and future-proofing. > Project:M36 can be used as an in-process or remote DBMS. > Project:M36 is written entirely in the Haskell programming language.

ThinkBeat 2y ago

On Microsoft SQL Server you can use native .Net to write stored procedures and functions.

kthielen 2y ago

I made something like this for Morgan Stanley some years ago, a structurally typed eager variant of Haskell with static elimination of type class constraints (so no runtime penalty for overloading) and uses LLVM for the back-end: http://github.com/morgan-stanley/hobbes/ http://github.com/morgan-stanley/hobbes/ We used it for processing and analyzing billions of events per day. Using structural algebraic types let us encode market data (obviously) but also complex data structures inside trading systems that we could correlate with market data. As you say, Haskell-ish expressions are much more compact and capable than SQL, which was one of the reasons I wanted to build it. It also had a somewhat novel compression method (“types as probabilities” if you like the old Curry-Howard view), which was very important to manage billions of daily events. Good times.

whateveracct 2y ago

Sooooo if you use a SQL database and a Haskell access library, you kind of get this. Like esqueleto for instance. With it, you basically use Haskell as a meta-programming language for SQL. It's really nice when it works. But yeah..makes me think that a more first-class thing would be even better. Tbh, maybe Haskell compiled to a lower-level query language would be better. A language that is about tables and btrees etc. Where there's no planner because the low-level language is the plan.

lmz 2y ago
Most planners use statistics. A fixed plan may not be optimal (and at the same time, statistics may be out of date).

tehlike 2y ago

As far as query languages go, you may want to look into prql, kusto or google's alternative (i forgot its name). They are composable, and more natural.