I didn't want to sidetrack you with this. I just wanted to know if I understood correctly. I believe this is nothing you need to worry about at this time. Thanks.
Ah ok. I guess that means when a user leaves the team, you have to re-encrypt the codebase with a new symetric key (as the user would still know the old symetric key)?
Why did those employees have access to such sensitive data? We could argue about the legal requirement to submit this data in general, but I really don't understand why (most of) this data isn't stored in an encrypted way and only accessible by a few people in the company.
Ah, I see. So there's a replication process similar to ClickHouse's MaterializedPostgres. Ideally, there would be functionality allowing a columnstore query to wait until all writes to the OLTP tables — up to the query's execution time — are available. This would make the system truly Postgres-native and address issues that no other system currently solves.
That sounds awesome. Are you saying you still use your normal OLTP table for writing data and the columnstore table is always in sync with that OLTP table (that's fantastic)? I ready it works with duckdb - how does it work? I guess there's no chance this is going to be available on Azure Flexible Server anytime soon.
Haha. No I'm not from Israel. Just a Star Trek fan:).
But thanks for the info. My issue with that is that I don't want to give a way my phone number, and I certainly don't want to pay for a service that gives me a phone number.
1. I'd like a native way to scale horizontally based on tenant ids without using citus.
2. array constraints (foreign keys) -> meaning that each item in the array references an id in another table.
I wish Joplin had better collaboration. I want an e2e encrypted, cloud-based solution my entire team can use. Notion UX is great but is useless to me without e2e encryption - and it becomes expensive for teams. Skiff marketed itself as secure but was immediately acquired by Notion.