title: Coming from MySQL, Going to Oracle: the Pitfalls
body: <p>All my development life I have only worked with MySQL for extended periods of time, and for a client we now need to work with an Oracle database for some performance testing and tuning.</p>
  
  <p>Any obvious pitfalls in moving from working with MySQL to Oracle I should watch out for?</p>
  
  <p>The things I discovered so far:</p>
  
  <ul>
  <li>There is only one database</li>
  <li>What MySQL calls a database is a Schema in Oracle</li>
  <li>A User and Schema is almost the same (still unclear of the differences here)</li>
  <li>There is no auto increment. Instead you need to create your own sequence</li>
  <li>Inserting multiple entries at the same time through multiple literal value tuples is not possible.</li>
  <li>Numeric formats are localized, which can cause headaches when importing from CSV files.</li>
  </ul>
  
  <p>Other tips would be greatly appreciated. Any good resources/documented past experiences with the transition would also be welcome. Note that we're not actually migrating a database from one to the other, it is more about the adjustments I'd have to make personally in my way of thinking etc.</p>