From 510ac75c5188b2a960c80f64c9db64431d4c13fb Mon Sep 17 00:00:00 2001
From: Christian Bauer <christian@hibernate.org>
Date: Wed, 16 Feb 2005 11:53:41 +0000
Subject: [PATCH] Correction

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@5743 1b8cb986-b30d-0410-93ca-fae66ebed9b2
---
 reference/en/modules/best_practices.xml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/reference/en/modules/best_practices.xml b/reference/en/modules/best_practices.xml
index a9400b5669..7cd1c1cf3d 100644
--- a/reference/en/modules/best_practices.xml
+++ b/reference/en/modules/best_practices.xml
@@ -1,4 +1,4 @@
-<chapter id="best-practices" revision="2">
+<chapter id="best-practices" revision="3">
     <title>Best Practices</title>
 
     <variablelist spacing="compact">
@@ -18,8 +18,9 @@
                 <para>
                     Hibernate makes identifier properties optional. There are all sorts of reasons why
                     you should use them. We recommend that identifiers be 'synthetic' (generated, with
-                    no business meaning) and of a non-primitive type. For maximum flexibility, use
-                    <literal>java.lang.Long</literal> or <literal>java.lang.String</literal>.
+                    no business meaning). It doesn't make a difference if you use <literal>long</literal>
+                    or <literal>java.lang.Long</literal>; primitives might be syntactically easier to handle
+                    though.
                 </para>
             </listitem>
         </varlistentry>