SQLToy
103 points
4 months ago
| 7 comments
| github.com
| HN
tekknolagi
4 months ago
[-]
Yesterday I found this and ported it to Python: https://github.com/tekknolagi/db.py

It's ~150LOC but doesn't have aggregates (yet)

reply
emmelaich
4 months ago
[-]
Did you use the same data? I couldn't find it in the original.
reply
tekknolagi
4 months ago
[-]
What do you mean same data?
reply
emmelaich
4 months ago
[-]
I mean the data / tables used. The tables used in the original.
reply
tekknolagi
4 months ago
[-]
I made up some stuff for tests and copied some tables from their demos
reply
wood_spirit
4 months ago
[-]
It’s like a ray tracer: every programmer should write a toy sql engine!

A very long time ago I started writing a game in a weekend a for Ludum dare competition and ended up writing a toy sql engine of my own https://williame.github.io/post/59997353762.html

I still get the urge to make a proper one one day. With the sql features that I wish sql engines had. Hmmm. Need-sniping myself now… :)

reply
boobsbr
4 months ago
[-]
Every programmer should also write a CPU and computer out of NAND gates: https://www.nand2tetris.org
reply
chunkyks
4 months ago
[-]
reply
barbegal
4 months ago
[-]
Great toy but it's a bit misleading not to touch on the query planner. All real SQL implementations will plan how to most efficiently run a query so the order of operations can be wildly different to expected based on the data and indexes available. This kind of tutorial makes it look like joins are very inefficient whereas a real database may make them highly efficient for a given query.
reply
halostatue
4 months ago
[-]
I had fun over the last day implementing this two ways in Elixir: https://github.com/halostatue/sqltoy_elixir.
reply
curtisblaine
4 months ago
[-]
I hoped this had a toy implementation of sql indices, but it looks like that's not the case: it just sorts the whole table on the fly on an ORDER BY.
reply
aboodman
4 months ago
[-]
I mean that basically in an implementation of indexes. Move the on-the-fly sorts to behind a command, then change the insert/delete code to maintain them, and voila - indexes.
reply
curtisblaine
4 months ago
[-]
Aren't indexes a static, pre-calculated way to avoid in-memory sorting on the fly?
reply
jrop
4 months ago
[-]
I love projects like this that shed light on and demystify and otherwise mysterious process. Thanks for sharing!
reply
tmountain
4 months ago
[-]
Great way to learn!
reply
dcreater
4 months ago
[-]
Would be great if it was literally any other language other than js
reply
RodgerTheGreat
4 months ago
[-]
It would be very easy to follow along with a transliteration into any dynamic language language with halfway decent support for functional programming.
reply
mhio
4 months ago
[-]
Why is that? There doesn't seem to be anything particularly esoteric in the implementation.
reply
tekknolagi
4 months ago
[-]
reply