I've been requested the flowing question within an interview:

"Exactly what does it mean with an isolated transaction in Java?"

I'm able to think about the Acidity qualities and Connection interface static fields, though I'm unsure exactly what the correct response to this is. Can anybody elaborate a solution?

When transaction is isolated it's resulted in no exterior occasions can impact consequence of transaction after it began. It will act as if it's the only real transaction went at any given time.

Isolation transaction is about the information consistency, that is described nicely in the link that follows.

http://biese.wordpress.com/2007/11/02/understand-database-isolation-levels/

ie.

Data consistency(Isolation transaction) is really a expression used to describe the precision of information. For example, suppose you've got a table that keeps a count of automobiles available available in vehicle shops. Whenever a vehicle is moved from car dealership A to car dealership B, the count needs to reduction in car dealership A and rise in car dealership B. Both actions must occur if a person happens and the other doesn't, the information becomes inaccurate—data inconsistency happens

.

Isolation of the transaction relates to compartmentalizing the information impacted by the transaction. This is often of numerous types eg. read_committed. This guarantees how other transactions begin to see the data even though it is still being modified with a transaction. You'll find more particulars @ http://download.oracle.com/javase/tutorial/jdbc/basics/transactions.html.