add a couple of links

This commit is contained in:
Gavin 2023-05-13 09:29:44 +02:00 committed by Christian Beikov
parent 83c192caeb
commit e0870fe3fe
1 changed files with 8 additions and 3 deletions

View File

@ -77,6 +77,7 @@ Where `{version}` is the latest version of the JDBC driver for your databse.
:slf4j: http://www.slf4j.org/ :slf4j: http://www.slf4j.org/
:enhancer: https://docs.jboss.org/hibernate/orm/5.4/topical/html_single/bytecode/BytecodeEnhancement.html :enhancer: https://docs.jboss.org/hibernate/orm/5.4/topical/html_single/bytecode/BytecodeEnhancement.html
:agroal: https://agroal.github.io
Optionally, you might also add any of the following additional features: Optionally, you might also add any of the following additional features:
@ -85,7 +86,7 @@ Optionally, you might also add any of the following additional features:
| Optional feature | Dependencies | Optional feature | Dependencies
| An {slf4j}[SLF4J] logging implementation | `org.apache.logging.log4j:log4j-core` or `org.slf4j:slf4j-jdk14` | An {slf4j}[SLF4J] logging implementation | `org.apache.logging.log4j:log4j-core` or `org.slf4j:slf4j-jdk14`
| A JDBC connection pool, for example, Agroal | For example, `io.agroal:agroal-pool` | A JDBC connection pool, for example, {agroal}[Agroal] | `org.hibernate.orm:hibernate-agroal` and `io.agroal:agroal-pool`, for example
| The Hibernate metamodel generator, if you're using the JPA criteria query API | `org.hibernate.orm:hibernate-jpamodelgen` | The Hibernate metamodel generator, if you're using the JPA criteria query API | `org.hibernate.orm:hibernate-jpamodelgen`
| Hibernate Validator | `org.hibernate.validator:hibernate-validator` and `org.glassfish:jakarta.el` | Hibernate Validator | `org.hibernate.validator:hibernate-validator` and `org.glassfish:jakarta.el`
| Compile-time checking for your HQL queries | `org.hibernate:query-validator` | Compile-time checking for your HQL queries | `org.hibernate:query-validator`
@ -200,11 +201,14 @@ SessionFactory sf = new Configuration()
The `Configuration` class has survived almost unchanged since the very earliest (pre-1.0) versions of Hibernate, and so it doesn't look particularly modern. The `Configuration` class has survived almost unchanged since the very earliest (pre-1.0) versions of Hibernate, and so it doesn't look particularly modern.
On the other hand, it's very easy to use, and exposes some options that `persistence.xml` doesn't support. On the other hand, it's very easy to use, and exposes some options that `persistence.xml` doesn't support.
:native-bootstrap: https://docs.jboss.org/hibernate/orm/6.2/userguide/html_single/Hibernate_User_Guide.html#bootstrap-native
:boot: https://docs.jboss.org/hibernate/orm/6.2/javadocs/org/hibernate/boot/package-summary.html
.Advanced configuration options .Advanced configuration options
**** ****
Actually, the `Configuration` class is just a very simple facade for the more modern, much more powerful—but more complex—API defined in the package `org.hibernate.boot`. Actually, the `Configuration` class is just a very simple facade for the more modern, much more powerful—but more complex—API defined in the package `org.hibernate.boot`.
This API is useful if you have very advanced requirements, for example, if you're writing a framework or implementing a container. This API is useful if you have very advanced requirements, for example, if you're writing a framework or implementing a container.
You'll find more information in the Hibernate ORM Integration Guide, and in the package-level documentation of `org.hibernate.boot`. You'll find more information in the {native-bootstrap}[User Guide], and in the {boot}[package-level documentation] of `org.hibernate.boot`.
**** ****
[[basic-configuration-settings]] [[basic-configuration-settings]]
@ -239,8 +243,9 @@ The properties you really do need to get started are these three:
==== ====
In Hibernate 6, you don't need to specify `hibernate.dialect`. In Hibernate 6, you don't need to specify `hibernate.dialect`.
The correct Hibernate SQL `Dialect` will be determined for you automatically. The correct Hibernate SQL `Dialect` will be determined for you automatically.
The only reason to specify this property is if you're using a custom user-written `Dialect` class. The only reason to specify this property is if you're using a custom user-written `Dialect` class.
Similarly, neither `hibernate.connection.driver_class` nor `jakarta.persistence.jdbc.driver` is needed when working with one of the supported databases.
==== ====
Pooling JDBC connections is an extremely important performance optimization. Pooling JDBC connections is an extremely important performance optimization.