4 ms·
Things I would like in a database: - All changes stored as diff trees with signed cryptographic hashes. I want to check out the state of the world at a specifi
by 0xbadcafebee 5y ago
Things I would like in a database:
- All changes stored as diff trees with signed cryptographic hashes. I want to check out the state of the world at a specific commit, write a change, a week later write another change, revert the first change 3 weeks later. And I want it atomic and side-loaded with no performance hit or downtime.
- Register a Linux container as a UDF or stored procedure. Use with pub/sub to create data-adjacent arbitrary data processing of realtime data
- Fine-grained cryptographically-verified least-privilege access control. No i/o without a valid short-lived key linked to rules allowing specific record access.
- Virtual filesystem. I want to ls /db/sql/SELECT/name/IN/mycorp/myproduct/mysite/users/logged-in/WHERE/Country/EQUALS/USA. (Yes, this is stupid, but I still want it. I don't want to ever have to figure out how to connect to another not-quite-compatible SQL database again.)
- sa46 5y ago> I want to check out the state of the world at a specific commit, write a change, a week later write another change, revert the first change 3 weeks later. This is sort of like temporal tables but with the ability to branch from a previous point of history. I'm not sure it would play well with foreign keys. You could branch the entire database with either point-in-time recovery or with the file-system using ZFS. Postgres.ai turned this into a product.