DUDE I was daydreaming about this the other day, but with postgres. Can I ask why you chose clickhouse? My idea was that every op could be an insert, and then the resulting state would be a transaction and logged? So you'd get basically logged cpu state? Idk cool stuff I'm pumped to dive in tonight.
caust1c 19 hours ago [-]
Spencer is an engineer at ClickHouse, so it makes sense.
meepmorp 21 hours ago [-]
based on this line from the readme, the answer to your question is likely "because":
> This emulator makes ClickHouse truly Turing complete. We are one step closer to running ClickHouse in ClickHouse.
blyry 20 hours ago [-]
lol for sure, I'm genuinely curious though, like maybe op is a clickhouse dev? Or maybe they had the cursed idea and decided clickhouse was the best fit for various reasons?
jitl 20 hours ago [-]
Postgres does not have incremental view maintenance for its materialized views like clickhouse does. This means the implementation strategy would need to be quite different. Perhaps triggers is enough and of course if you use functions then sure, you can make an emulator there too.
blyry 20 hours ago [-]
okay did like 10 seconds of introspection and OP probably isn't the repo author, and the repo author definitely looks like they work at clickhouse
cptnapalm 21 hours ago [-]
"Because" is always the most fun reason.
hobs 20 hours ago [-]
This is amazing, and also psychic damage inducing - I thought I had seen some terrifying SQL things and then I see "ClickOS UDF"
Rendered at 10:34:18 GMT+0000 (Coordinated Universal Time) with Vercel.
> This emulator makes ClickHouse truly Turing complete. We are one step closer to running ClickHouse in ClickHouse.