title: How Do I Deal With Django Session Data for Storing Users ID?
body: <p>This may sound too easy to understand but I am not sure I am having my head around it.</p>
  
  <p>When a user is signing up in the first page of my app, I have <code>request.session['user_id']</code> set which is used in page two of the sign up to complete registration. The <code>user_id</code> is the primary key to user in <strong>USER TABLE</strong> but I don't want to store user_id in <code>session</code>. I fear it might be tampered with and the <strong>WRONG</strong> row might get updated.</p>
  
  <p>I would want something like a <em>token</em> that would be generated by my script but <strong>Django's SESSION TABLE</strong> only has three columns (<em>session_key, session_data, expire_date</em>) and it saves session details to it automatically. </p>
  
  <p>My questions precisely are:</p>
  
  <ol>
  <li>Can I tinker with the <strong>SESSION TABLE</strong> and add a <code>session_token</code> to it or I have to create my own table?</li>
  <li>How do I get the <code>session_token</code> to automatically save like other columns in Django <strong>SESSION TABLE</strong>?</li>
  <li>Or is `request.session['user_id'] okay and safe?</li>
  <li>Do all these also apply to <strong>COOKIES</strong> and why do I need to use cookies when <code>SESSION_EXPIRE_AT_BROWSER_CLOSE</code> is set to <code>FALSE</code>?</li>
  </ol>