4 ms·
Just curious for people who are advocating for email how they deal with the following situations: 1. The user gets a new email address. Instead of updating the
by nodamage 9y ago
Just curious for people who are advocating for email how they deal with the following situations:
1. The user gets a new email address. Instead of updating the email address on their existing account, they create a new account. Then they are confused when none of their data from their old account shows up when they login to the new one.
2. The user gets a new email address and no longer has access to the old one. Then they forget their password and are unable to reset it because the reset email is going to a dead email address.
- bsvalley 9y ago1. This looks like a normal use case. It depends on your business, if you end up collecting more than just an email (e.g. SSN, phone #, etc.), then you can add a logic to prevent the creation of a new account from the same user. Otherwise, it looks just like the creation of a new account and shouldn't be handled has an exception by your app. 2. On the user side you only present an email as a login. Though, on the implementation side you still need a user_id as your primary key. You can update the email attribute at anytime for an existing user_id. That involves an extra step to setup some sort of security questions so that a user can update the email address without having to access the account.