From 01dcf0687db10045c65e51b04dcc771459125abc Mon Sep 17 00:00:00 2001 From: Gavin Date: Sun, 7 May 2023 18:41:05 +0200 Subject: [PATCH] more on XxxxNamingStrategy --- .../src/main/asciidoc/introduction/Configuration.adoc | 9 ++++++--- .../asciidoc/introduction/Hibernate_Introduction.adoc | 2 +- 2 files changed, 7 insertions(+), 4 deletions(-) diff --git a/documentation/src/main/asciidoc/introduction/Configuration.adoc b/documentation/src/main/asciidoc/introduction/Configuration.adoc index 1d8b41bf6a..1a1c5c8268 100644 --- a/documentation/src/main/asciidoc/introduction/Configuration.adoc +++ b/documentation/src/main/asciidoc/introduction/Configuration.adoc @@ -309,14 +309,17 @@ annotations which we'll discuss below in <>: | `hibernate.default_schema` | A default schema name for entities which do not explicitly declare one | `hibernate.default_catalog` | A default catalog name for entities which do not explicitly declare one | `hibernate.physical_naming_strategy` | A `PhysicalNamingStrategy` implementing your database naming standards +| `hibernate.implicit_naming_strategy` | An `ImplicitNamingStrategy` which specifies how "logical" names of + relational objects should be inferred when no name is specified in + annotations |=== [TIP] .Implement your naming standards as a `PhysicalNamingStrategy` ==== -Writing your own `PhysicalNamingStrategy` is an especially good -way to reduce the clutter of annotations on your entity classes, and -we think you should do it for any nontrivial data model. +Writing your own `PhysicalNamingStrategy` and/or `ImplicitNamingStrategy` is an especially good way to reduce the clutter of annotations on your entity classes, and we think you should do it for any nontrivial data model. + +Please refer to the Javadoc for these interfaces for more information about the division of responsibility between them. ==== === Nationalized character data in SQL Server diff --git a/documentation/src/main/asciidoc/introduction/Hibernate_Introduction.adoc b/documentation/src/main/asciidoc/introduction/Hibernate_Introduction.adoc index 1490befb1f..5ff205b86f 100644 --- a/documentation/src/main/asciidoc/introduction/Hibernate_Introduction.adoc +++ b/documentation/src/main/asciidoc/introduction/Hibernate_Introduction.adoc @@ -45,7 +45,7 @@ Hibernate was the inspiration behind the _Java_ (now _Jakarta_) _Persistence API .The early history of Hibernate and JPA ==== The Hibernate project began in 2001, when Gavin King's frustration with Entity Beans in EJB 2 boiled over. -It quickly overtook other open source and commercial contenders to become the most popular persistence solution for Java, and the book _Hibernate in Action_, written with Christian Bauer, was an influential best-seller. +It quickly overtook other open source and commercial contenders to become the most popular persistence solution for Java, and the book _Hibernate in Action_, written with Christian Bauer, was an influential bestseller. In 2004, Gavin and Christian joined a tiny startup called JBoss, and other early Hibernate contributors soon followed: Max Rydahl Andersen, Emmanuel Bernard, Steve Ebersole, and Sanne Grinovero.