> PostgreSQL takes FOR UPDATE on rows before a DELETE, or before an UPDATE that modifies a column that is part of a unique index that neither contains expressions nor is partial
This also happens when you UPDATE the same row twice within the same transaction.
I don’t fall out with the change at all, but being given 1 month to migrate doesn’t seem well thought out, there will definitely be some avoidable negative sentiment related to that.
These are potential paying users not freeloaders to evict.
This is the only real problem I have with how they handled the situation. But it's a big problem.
Whether or not these folks on free plans are ever going to convert to paid, they trusted PlanetScale to serve as a critical building block for their project/business. I think the least they could do is ease the transition by offering them a reasonable amount of time to offboard.
I personally would never trust critical infra to a company that has ever abruptly terminated a product offering with only 1 month notice.
> The Zig language accepts hard tabs and carriage returns. The self-hosted compiler implements the Zig language correctly; accepting hard tabs and carriage returns. However, the self-hosted compiler is not yet complete, and what people are using in reality is the stage1 compiler, which does not accept hard tabs.
You are confusing a layoff and a furlough. It's not your fault though, the Portuguese government decided to call a furlough a layoff for who knows what reason.
Thanks for that updated link, I first saw it through the netflix repo but bundler on my project pulled from that more recent repo and I got the repos confused.
