Correction
git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@5743 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
parent
d62693589c
commit
510ac75c51
|
@ -1,4 +1,4 @@
|
||||||
<chapter id="best-practices" revision="2">
|
<chapter id="best-practices" revision="3">
|
||||||
<title>Best Practices</title>
|
<title>Best Practices</title>
|
||||||
|
|
||||||
<variablelist spacing="compact">
|
<variablelist spacing="compact">
|
||||||
|
@ -18,8 +18,9 @@
|
||||||
<para>
|
<para>
|
||||||
Hibernate makes identifier properties optional. There are all sorts of reasons why
|
Hibernate makes identifier properties optional. There are all sorts of reasons why
|
||||||
you should use them. We recommend that identifiers be 'synthetic' (generated, with
|
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
|
no business meaning). It doesn't make a difference if you use <literal>long</literal>
|
||||||
<literal>java.lang.Long</literal> or <literal>java.lang.String</literal>.
|
or <literal>java.lang.Long</literal>; primitives might be syntactically easier to handle
|
||||||
|
though.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
Loading…
Reference in New Issue