We can see the following notes in the environments. When use * java.sql.driverManager ) * * This shows that we can configure the transaction isolation level of the database in hibernate.cfg.xml, in general, the database The isolation level is classified as follows: SQL transaction isolation level isolation level Dirty Read illegibility (read uncommitted) may be possible to read committed (read committed) is not possible Possible readable reads cannot be critical (serializable) cannot be unlikely.
Don't underestimate this comment, I am making mistakes today:
// ..... Transaction A Start TIME_LIMIT_PROCESS TLP = ProcessLimitFacade.getlimitByProcessId (DPDTO .GetProcessinsCtrl ()); TLP.SetStatus (2); ProcessLimitFacade.Update (TLP); // This method uses additional transaction B //. ..... Transaction A ends
The results can be seen! It is difficult to put it in the Update method. The procedure is permanently stopped in that way, it seems to have entered a black hole .........
Also, you should mention that the SQL standard provides for the transaction isolation level, which does not necessarily have such problems, do not necessarily happen; so different databases are different from the level of transaction isolation, such as Some databases treat repeatable read levels to be serialized.
