FIx typo
This commit is contained in:
parent
1fa0694d6f
commit
9d4d728867
|
@ -189,7 +189,7 @@ The value for `hibernate.connection.isolation` can be specified in one of 3 form
|
|||
* the integer value accepted at the JDBC level.
|
||||
* the name of the `java.sql.Connection` constant field representing the isolation you would like to use.
|
||||
For example, `TRANSACTION_REPEATABLE_READ` for https://docs.oracle.com/javase/8/docs/api/java/sql/Connection.html#TRANSACTION_REPEATABLE_READ[`java.sql.Connection#TRANSACTION_REPEATABLE_READ`].
|
||||
Not that this is only supported for JDBC standard isolation levels, not for isolation levels specific to a particular JDBC driver.
|
||||
Note that this is only supported for JDBC standard isolation levels, not for isolation levels specific to a particular JDBC driver.
|
||||
* a short-name version of the java.sql.Connection constant field without the `TRANSACTION_` prefix. For example, `REPEATABLE_READ` for https://docs.oracle.com/javase/8/docs/api/java/sql/Connection.html#TRANSACTION_REPEATABLE_READ[`java.sql.Connection#TRANSACTION_REPEATABLE_READ`].
|
||||
Again, this is only supported for JDBC standard isolation levels, not for isolation levels specific to a particular JDBC driver.
|
||||
|
||||
|
@ -260,4 +260,4 @@ Hibernate abstracts over variations between dialects of SQL via the class `org.h
|
|||
- Additional community-supported ``Dialect``s are available in the separate module `hibernate-community-dialects`.
|
||||
|
||||
In Hibernate 6, it's no longer necessary to explicitly specify a dialect using the configuration property `hibernate.dialect`, and so setting that property is now discouraged.
|
||||
(An exception is the case of custom user-written ``Dialect``s.)
|
||||
(An exception is the case of custom user-written ``Dialect``s.)
|
||||
|
|
Loading…
Reference in New Issue