title: Achieving ACID properties using JDBC?
body: <p>First of all i would like to confirm is it the responsibility of developer to follow these properties or responsibilty of transaction Apis like JDBC?</p>
  
  <p>Below is my understanding how we achieve acid properties in JDBC</p>
  
  <p>Atomicity:- as there is one transaction associated with connection, so we do commit or rollback , there are no partial updation.Hence achieved</p>
  
  <p>Consitency:- when some data integrity constraint is voilated (say some check constraint) then sqlexception will be thrown . Then programmer acieve the consistent database by rollbacking the transaction?</p>
  
  <p>one question on above say  we do transaction1 and sql excpetion is thrown during transaction 2 as explained above . Now we catch the exception and do the commit will first transaction be commited?</p>
  
  <p>Isolation:- Provided by JDBC Apis.But this leads to the problem of concurrent update . so it has be dealt manually right?</p>
  
  <p>Durability:- Provided by JDBC Apis.</p>
  
  <p>Please let me if above understanding is right?</p>