title: Table without a primary key
body: <p>So I've always been told that it's absolutely necessary to have a primary key specified with a table. I've been doing some work and ran into a situation where a primary key's unique constraint would stop data I need from being added.</p>
  
  <p>If there's an example situation where a table was structured with fields:</p>
  
  <pre><code>Age, First Name, Last Name, Country, Race, Gender
  </code></pre>
  
  <p>Where if a TON of data was being entered all these fields don't necessarily uniquely identify a row and I don't need an index across all columns anyways. Would the only solution here be to make an auto-incrementing ID field? Would it be okay to NOT have a primary at all?</p>