Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

more presentation cleanups

This commit is contained in:
Gavin 2023-05-12 22:26:09 +02:00 committed by Christian Beikov
parent 59b6f702e5
commit 96b503454e
4 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
documentation/src/main/asciidoc/introduction/Configuration.adoc
View File

@ -149,11 +149,10 @@ The `<persistence-unit>` element defines a named _persistence unit_, that is:
Each `<class>` element specifies the fully-qualified name of an entity class. Each `<class>` element specifies the fully-qualified name of an entity class.
[TIP] .Scanning for entity classes
// .Scanning for entity classes ****
====
In some container environments, for example, in any EE container, the `<class>` elements are unnecessary, since the container will scan the archive for annotated classes, and automatically recognize any class annotated `@Entity`. In some container environments, for example, in any EE container, the `<class>` elements are unnecessary, since the container will scan the archive for annotated classes, and automatically recognize any class annotated `@Entity`.
==== ****
Each `<property>` element specifies a _configuration property_ and its value. Each `<property>` element specifies a _configuration property_ and its value.
Note that: Note that:

1
documentation/src/main/asciidoc/introduction/Hibernate_Introduction.adoc
View File

@ -182,6 +182,7 @@ So there's that.
One thing that some repository frameworks offer is the ability to declare an abstract method that queries the database, and have the framework fill in an implementation of the method. One thing that some repository frameworks offer is the ability to declare an abstract method that queries the database, and have the framework fill in an implementation of the method.
But the way this works is that you must encode your query into the name of the method itself. But the way this works is that you must encode your query into the name of the method itself.
Which, at least in principle, for a not-very-complicated query, leads to a method name like this: Which, at least in principle, for a not-very-complicated query, leads to a method name like this:
[.text-center] [.text-center]

2
documentation/src/main/asciidoc/introduction/Interacting.adoc
View File

@ -429,7 +429,7 @@ List<Book> matchingBooks =
When a query has multiple parameters, named parameters tend to be easier to read, even if slightly more verbose. When a query has multiple parameters, named parameters tend to be easier to read, even if slightly more verbose.
[IMPORTANT] [WARNING]
// .Using parameters to avoid injection attacks // .Using parameters to avoid injection attacks
==== ====
_Never_ concatenate user input with HQL and pass the concatenated string to `createSelectionQuery()`. _Never_ concatenate user input with HQL and pass the concatenated string to `createSelectionQuery()`.

8
documentation/src/main/style/asciidoctor/css/hibernate-layout.css
View File

@ -11,7 +11,13 @@ body:before {
#header { #header {
width: 1000px !important; width: 1000px !important;
} }
#toctitle,.sidebarblock>.content>.title,h4,h5,h6{ .sidebarblock>.content>.title,h4,h5,h6{
font-size: 1.3em !important;
margin-top:0em !important;
margin-bottom:1em !important;
line-height:1.0125em !important
}
#toctitle>.content>.title,h4,h5,h6{
font-family:"Open Sans","DejaVu Sans",sans-serif !important; font-family:"Open Sans","DejaVu Sans",sans-serif !important;
font-weight:300 !important; font-weight:300 !important;
font-style:normal !important; font-style:normal !important;