I am designing a system and I don\'t think it\'s a good idea to give the ability to the end user to delete entries in the database. I think that way because often then end u
I suggest having a second database like DB_Archives whre you add every row deleted from DB. The is_active field negates the very purpose of foreign key constraints, and YOU have to make sure that this row is not marked as deleted when it's referenced elsewhere. This becomes overly complicated when your DB structure is massive.