aleda145.bsky.social
building kavla.dev, open source data canvas https://github.com/aleda145/kavla
👤 Joined on 03 April 2026
Followers
Following
Total Posts
@aleda145.bsky.socialhaha the accidental select * at 1am is a rite of passage. duckdb saving you from your own query is a nice safety net to have
Show Postthe {} trigger is a nice touch. first thing i'd do is put a knob on the LIMIT and drag it to a million just to see what happens, so maybe a max on those
Show Postthe {} trigger is slick, feels like a jupyter widget inside sql. what happens if the user types a value that would blow up the query?
Show PostRestore plus download is a good pair: the download is what saves you when the history itself is the thing that got messed up. With a cap on saves to keep, I'd also let people pin one save so it never rotates out.
Show Postkeeping a 'before restoration' save is a nice touch, so the restore itself can be undone 😅
Show Post