title: Table design for user's information as well as login credentials?
body: <p>Initially I would like to ask you to forget about hashing passwords or w/e related to passwords, this question is not related to securing passwords, etc and I do know/understand how this should be done.</p>
  
  <p><strong>What is the best approach to store the data in question, considering performance on read/write - to build one or more tables?</strong></p>
  
  <p>Single table, for example:</p>
  
  <blockquote>
    <p>Table users: id, username, password, hash, email,
    group, access, address, phone,
    parents, ts_created, ts_update</p>
  </blockquote>
  
  <p>Multiple tables, for example:</p>
  
  <blockquote>
    <p>Table users: id, username, password,
    hash, email, group, access,
    ts_created, ts_update</p>
    
    <p>Table user's information: id, user_id,
    address, phone, parents, ts_created,
    ts_update</p>
  </blockquote>
  
  <p>What if your user's information fields may grow along the time - how should you deal with it ?</p>
  
  <blockquote>
    <p>For example new fields:
    birthday_date, comments, situation</p>
  </blockquote>
  
  <p>Will having 2 tables be slower on queries than having a single table ? </p>
  
  <p>If having multiple tables in this case is only for maintaining a good design with separated data, does that mean it is not useful at all for performance reasons ?</p>
  
  <p><strong>If you want real sql examples let me know and I will scrap something to update this.</strong></p>