Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Transactions ACID Advice

 
Ranch Hand
Posts: 18944
  • Mark post as helpful
  • send pies
  • 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..
 
Without subsidies, chem-ag food costs four times more than organic. Or this tiny ad:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
    Bookmark Topic Watch Topic
  • New Topic