From 2f236d64168278deb5977114ef425a12ffd96011 Mon Sep 17 00:00:00 2001 From: Diego Plentz Date: Wed, 4 Jul 2007 06:01:25 +0000 Subject: [PATCH] [HHH-2487] Typo in "5.1.7. version (optional)" git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@12723 1b8cb986-b30d-0410-93ca-fae66ebed9b2 --- .../manual/en-US/src/main/docbook/modules/basic_mapping.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml b/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml index 861fdf39e1..eaaefe7122 100644 --- a/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml +++ b/documentation/manual/en-US/src/main/docbook/modules/basic_mapping.xml @@ -1376,7 +1376,7 @@ A version or timestamp property should never be null for a detached instance, so - Hibernate will detact any instance with a null version or timestamp as transient, + Hibernate will detect any instance with a null version or timestamp as transient, no matter what other unsaved-value strategies are specified. Declaring a nullable version or timestamp property is an easy way to avoid any problems with transitive reattachment in Hibernate, especially useful for people