3 ms·
Because many items don't make sense without showing old deleted data. Imagine you run a shop with a list of products. People can order and receive products fro
by gridspy 4y ago
Because many items don't make sense without showing old deleted data.
Imagine you run a shop with a list of products. People can order and receive products from you. View past orders and get invoices and recepts.
One day you have a product that has reached end of life, or isn't selling well. So naturally you delete it from the store.
If you actually deleted this item, all the old invoices wouldn't be able to refer to it. Old customers couldn't claim warranty on it. You couldn't create old sales reports that made sense.
Turns out that this problem extends to most tables. Old clients? Users? Products? Invoices? In most cases outright deletion makes many other things invalid that you want to keep. So it's nice when the ORM makes meeting this requirement easy for you.
All this in addition to the ability to recover from an accidental or temporary deletion.
- hgsgm 4y ago"Don't delete stuff you are still using" has nothing to do with "delete stuff you shouldn't be using and in many jurisdictions cannot legally possess".
- macintux 4y agoThe latter category is typically small, a recent legal development, and absolutely impossible for an ORM to identify sans explicit rules.