3 ms·
This is all fine and well until you need to measure "how many users reset their passwords" or "what is the bounce rate of users confirming their email addresses
by randerson 12y ago
This is all fine and well until you need to measure "how many users reset their passwords" or "what is the bounce rate of users confirming their email addresses". This may be useful for avoiding sensitive data, but it's not a practical substitute for writing to the database, nor is it really that much effort to create two database tables.
- morgante 12y agoThat sort of data belongs in an analytics or event database (ie. one with entirely different requirements from your normal database). Usually when I implement a stateless approach like this I still fire off a log event every time we generate a password reset.