title: Oracle DB's Isolation levels and JDBC's TRANSACTION_NONE attribute
body: <p>I am trying to understand the isolation levels in Oracle. I have a question about the NONE isolation level. </p>
  
  <p>I can understand the other 4 cases and what it means. Basically each one has a type of lock that gets applied to either the row or table for locking access to other transactions. I tested this in code and I see the updates blocking on other transactions running on the same row. </p>
  
  <p>If I set the isolation level to none, does it mean that if there are two different processes writing to the same row in database, it will overwrite each other or may be corrupt the data? What does it mean to have no transactions? And what implications could it have? </p>
  
  <p>ref: <a href="http://docs.oracle.com/javase/tutorial/jdbc/basics/transactions.html#transactions_data_integrity" rel="nofollow">http://docs.oracle.com/javase/tutorial/jdbc/basics/transactions.html#transactions_data_integrity</a></p>