3 ms·
Happy to answer any questions that might be left lingering on what happened here.
by tommoor 3y ago
Happy to answer any questions that might be left lingering on what happened here.
- uhoh-itsmaciek 3y agoWhat do you think about the TRUNCATE ... CASCADE functionality in terms of UX? The docs clearly state what the behavior is [1], but I've worked on managed Postgres and Postgres tooling for over fifteen years now, and I can't say with certainty I would not have made the same mistake [2]. Do you think there's reasonable changes Postgres could make to the syntax or the mechanism around TRUNCATE to avoid accidents like this? [1]: https://www.postgresql.org/docs/current/sql-truncate.html https://www.postgresql.org/docs/current/sql-truncate.html [2]: I like to think I would have at least checked the docs because there's no efficient way for TRUNCATE ... CASCADE to work how you intended given how I know TRUNCATE is implemented, but who knows?
- tommoor 3y agoI wasn't personally aware of the migration until after it had been executed, but if I'd reviewed the PR I'm not confident I would have known any better. It doesn't feel intuitive that any table with any foreign keys gets completely wiped.