Queryable Executables • Hacker News Board

Re: Queryable Executables

#81

Post by punnerud » Wed, Aug 26, 2026, 3:44 PM UTC

inigyou wrote: post #75

punnerud wrote: post #47

I build a SQLite clone in Rust with this analogy in mind, and unlike SQLite it support multiple writers by giving them separate segment in a file. Calles the programming "language" PySpell, it converts Python into AST then into RUST with a lot of cool features you can enable when the database and programming language is living in the same place. http://github.com/punnerud/mpedb

This is AI slop (until proven otherwise).

Already using it as the primary DB in multiple off my apps and dev pipelines. I don't trust my own "slop", but the all the tests from SQLite, Python, PHP etc agains the DB

Re: Queryable Executables

#82

Post by inigyou » Wed, Aug 26, 2026, 4:09 PM UTC

punnerud wrote: post #81

inigyou wrote: post #75

Earlier quoted context omitted.

This is AI slop (until proven otherwise).

Already using it as the primary DB in multiple off my apps and dev pipelines. I don't trust my own "slop", but the all the tests from SQLite, Python, PHP etc agains the DB

I looked at some code. The CLI has comments about a feature where you can access a nonexistent database file without creating it but I doubt that actually works, as it seems to create the database file before processing commands. And I wonder if multi database actually works because it handles prefixes like "SELECT * FROM db.foo" by splitting it into db selector "db" and unprefixed statement "SELECT * FROM foo" which obviously wouldn't work if the statement accessed more than one database.

I also found comments about replacing identifiers in SQL (used to implement ALTER statements probably?) which say that it won't work right if two things in the database have the same name and it'll get caught by a sanity check later.

That's just the parts I looked at.

Re: Queryable Executables

#83

Post by zavec » Wed, Aug 26, 2026, 4:45 PM UTC

Between this and the nix/guix stuff, Farid is definitely becoming one of my favourite mad computer scientist bloggers, right up there with Justine.

(Or computer mad scientist? Whatever (mad scientist) && (computer scientist) is)