Timeline for Should we ever delete data in a database?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4, 2018 at 18:32 | comment | added | Stefan Falk | The EU GDPR sends their regards. | |
| Jan 15, 2016 at 21:33 | comment | added | gnasher729 | Credit card numbers. Should never be stored. Actually MUST never be stored. If a customer is stupid enough to send me their credit card number in an email, I have a real problem. There must be ways to get rid of it. | |
| Nov 7, 2012 at 15:23 | comment | added | TMN | Just to be pedantic, you should never store a password anywhere. You store the (one-way) encrypted result. If someone forgets their password, you generate a new one for them. There should be NO WAY to "recover" a password, because if you can do it, so can somebody else. | |
| Nov 6, 2012 at 21:04 | comment | added | Mike Partridge | This is a good point, but as to your password history example - you do often want to store old passwords so that you can make sure they're not a duplicate of any in the past 12 or whatever. Don't get me wrong - I don't like this policy, but I have implemented it, and it seems pretty common in enterprise-y apps. | |
| Aug 4, 2012 at 13:55 | comment | added | user4124 | Interesting. Do the big companies really implement this? | |
| Aug 4, 2012 at 9:07 | history | answered | Jakob | CC BY-SA 3.0 |