From c7a02c8051039b41b0003cfba5c1b2c00c8f4a03 Mon Sep 17 00:00:00 2001
From: Martin Goik <goik@hdm-stuttgart.de>
Date: Fri, 12 Dec 2014 10:06:21 +0100
Subject: [PATCH] Typos
---
Sda2/sda2.xml | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/Sda2/sda2.xml b/Sda2/sda2.xml
index 653d9c53f..2a135395c 100644
--- a/Sda2/sda2.xml
+++ b/Sda2/sda2.xml
@@ -3331,10 +3331,10 @@
<section xml:id="objectEqualityByNaturalKey">
<title>Object equality by natural key</title>
- <para>Defining entity equality based on database identity suffers a
- severe deficiency: Newly created instances invariably differ from
- any foreign non-identical instance regardless whether it does have a
- database identity or not. We consider an example:</para>
+ <para>Defining entity equality based on database identity suffers
+ from a severe deficiency: Newly created instances invariably differ
+ from any foreign non-identical instance regardless whether it does
+ have a database identity or not. We consider an example:</para>
<programlisting language="none">package session2;
...
@@ -3407,9 +3407,9 @@
implement <methodname>Object.equals(Object)</methodname> in a more
meaningful way. The problem comparing transient instances occurs
since a surrogate key's value is being provided by the database
- server when an entity is being persisted. If at least one natural
- key (sometimes referred to as <quote>business key</quote>) is being
- defined this one may be used instead:</para>
+ server only at the time an entity is being persisted. If at least
+ one natural key (sometimes referred to as <quote>business
+ key</quote>) is being defined this one may be used instead:</para>
<figure xml:id="implementEqualsByNaturalKey">
<title>Implementing <methodname>Object.equals(Object)</methodname>
--
GitLab