title: Google Sign-In, Database Side
body: <p>I've read about using Google to handle sign-ins from <a href="https://developers.google.com/accounts/docs/OAuth2Login" rel="noreferrer">this website</a>, but it doesn't explain very much about what should be going on with the database. </p>
  
  <p>Normally for user accounts in a database you'd have fields like <code>id</code>, <code>username</code>, <code>password</code>, etc. From what I read in the link, you will eventually get the ID token for a user, and inside is a key called "<code>sub</code>" that has a value in it that you can use to identify the user. </p>
  
  <p>My question is, where would this "<code>sub</code>" be stored in the database? 
  Would it go in the <code>id</code> field? <code>Username</code> field? </p>
  
  <p>I think it shouldn't go in the <code>username</code> field since there's the possibility that someone creates a username that is exactly the same as someone's Google <code>sub</code> id. But it also seems weird to put it in the <code>id</code> field. </p>
  
  <p>Also, would there need to be another field in the <code>user accounts</code> table that is a boolean in order to differentiate between users signed in natively and users signed in through Google?</p>