• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Transactions ACID Advice

 
Ranch Hand
Posts: 18944
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am executing a transaction against a single database.
AND HANDLE IT SO:
Connection.setAutocommit(false); // for ATOMICITY of ACID
Connection.setIsolationLevel(TRANSACTION_READ_COMMITTED); // for ISOLATION of ACID

PROBLEM:
I guess setAutocommit(false); is a Must FOR the 2nd stage... true?
B'cos I have some special insert queries which must execute in autocommit(true) modus. But I am handling all the DB-Story in a central way. I donot want to write extra if else else code for only those special conditions; in which I just do some insert and I am sure at least one of the fields of the indexes that are used will have a different value..
 
It would give a normal human mental abilities to rival mine. To think it is just a tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic