Hacker News new | past | comments | ask | show | jobs | submit login

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.



Someone wanted to get this done without waiting on the DBA team so they rolled some implicit schema instead.


This reminds me of a good use case for the Laravel Soft Deletes: https://laravel.com/docs/7.x/eloquent#soft-deleting.


love this feature so much


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.


Sure, but that just covers up the lie better. Maybe a flag "ToBeDeleted" and any stilled logged in sessions see account is scheduled for deletion.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: