In this chapter, we discussed the fundamental concepts behind transactions and caching, and how they are implemented in Hibernate.
Conceptually, a transaction is a group of operations that must be done reliably against a database or any other resource. Every transaction is specified by its so-called ACID properties: Atomicity, Consistency, Isolation, and Durability. Of these properties, only atomicity and isolation are of concern to the application developer. The other two are implemented internally by the transactional resource.
Hibernate allows you to configure transaction isolation through the configuration file. This is done through the
hibernate.connection.isolation entry in the configuration file with a value defined as a static member ...