Conversation

Notices

1. Jerod Santo (jerod@changelog.social)'s status on Wednesday, 26-Apr-2023 00:03:58 UTC Jerod Santo

   I like this alternative approach to soft delete:

   “Speaking from 30,000 feet, programming is all about tradeoffs. However, this is one of those rare places where as far as I can tell the cost/benefit skew is so disproportionate that the common platitude falls flat.”

   https://brandur.org/fragments/deleted-record-insert

   • Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Wednesday, 26-Apr-2023 00:08:35 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     @jerod I've been considering something similar when you have a migration that destroys data that presumably you don't want anymore: Have some slushbucket table where you throw that data, so that you can write a working rollback.

     I wouldn't roll back in prod, and any data added after the migration wouldn't have that legacy data anyway, so rollback would fail. But in dev it's really nice to have working rollback.