lyxell
Joined 5 years ago
Joined 5 years ago
I published it today! :)
Sorry, but this sounds like overly sensational marketing speak and just leaves a bad taste in the mouth for me.
See https://docs.rs/txtar/latest/txtar/ for an example
I created a repo for my solutions here: https://github.com/lyxell/aoc2024-sqlite
Update: Wow. Reading your solutions was a real eye-opener for me. It never struck me that one can exploit the fact that unmaterialized CTE's will not be evaluated for rows that is not needed by another SELECT and one can use this the same way one uses laziness in Haskell. This is great stuff, thanks again for sharing!
I realized when solving todays problem that SQLite’s
json_each("[" || T.c1 || "]")
Is useful for parsing comma separated rows into (row, col)-pairs as well.This is true with one exception, if you create an INTEGER PRIMARY KEY, SQLite will use this instead [1].