Databases
StackOverflow2013
Postsdbo
POArchitecture for merging multiple user accounts together
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POArchitecture for merging multiple user accounts together
    primarykey
    data
    text
    <p>Okay, I got a website where you can register yourself and login. You can also login with your facebook, twitter or linkedin account.</p> <p>It is important that users only have one account registered. So somehow, I want to merge the accounts of users if they use different methods to login. What is the best solution to solve this?</p> <p>For instance, the user logs in with his Facebook account. I use the data to register an account for him automatically. Should I sent an e-mail with an username and password of our website? (If this is okay with the policy of Facebook). Should I give them a second screen where they can fill in an username and password? But that's not the idea behind logging in with your Facebook account. It should simplify your procedure to participate.</p> <p>It's also possible the user has registered himself on our website and the next time he logs in with his twitter account. How can I merge these 2 accounts as one? What's the best way?</p> <p>So basically my question is: I got 4 different ways a user becomes a member of our website. How can I make sure all these 4 ways only create one account if a user decides to use multiple ways? What's the best flow to make sure that it doesn't become a hassle for the user himself?</p> <hr> <p>Edit: </p> <p>3 years after I asked this question, I am giving the answer myself in a series of articles: <a href="http://www.sitepoint.com/series/using-social-networks-as-a-login-system/" rel="noreferrer">http://www.sitepoint.com/series/using-social-networks-as-a-login-system/</a></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USP.T.
    1. USP.T.
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POArchitecture for merging multiple user accounts together
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POArchitecture for merging multiple user accounts together
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POArchitecture for merging multiple user accounts together
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOf course it's best to try to prevent a user from having multiple accounts in the first place by allowing multiple login methods like Stack Overflow, but even SO has the ability for moderators to merge accounts. I'm offering bounty for anyone who can describe an architecture to allow this. There has to be a better solution than "update post set UserID = 2 where UserID = 1"
      singulars
      1. POArchitecture for merging multiple user accounts together
      1. USDavid Boike
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload