Re:Instead of deleting account, NYT appends ‘1000’ to userna...
by emodendroket on Tuesday April 28, 2020 @09:50AM
(#23006922)
In that case it seems simpler to introduce an IsDeleted flag than to have a convention that 1000 goes on the end of the name.
[ Parent
| on HN ]
Re:Instead of deleting account, NYT appends ‘1000’ to userna...
by Bjartr on Tuesday April 28, 2020 @09:52AM
(#23006942)
Someone wanted to get this done without waiting on the DBA team so they rolled some implicit schema instead.
Re:Instead of deleting account, NYT appends ‘1000’ to userna...
by neovive on Tuesday April 28, 2020 @10:07AM
(#23007089)
This reminds me of a good use case for the Laravel Soft Deletes: https://laravel.com/docs/7.x/eloquent#soft-deleting.
Re:Instead of deleting account, NYT appends ‘1000’ to userna...
by marcofatica on Tuesday April 28, 2020 @10:10AM
(#23007119)
love this feature so much
Re:Instead of deleting account, NYT appends ‘1000’ to userna...
by nunez on Tuesday April 28, 2020 @12:20PM
(#23008535)
I'm learning about database design, and I'm learning that this might not be that easy if the relationships between users and other data on the site are ill-defined. There may be multiple tables in their design that will require knowledge of that flag, and it might legitimately be way easier to just add junk to the end of the user account than it is to introduce a new flag.