Apache
/
openjpa
mirror of https://github.com/apache/openjpa.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

OPENJPA-1376: Documentation update - be more specific about OpenJPA versions, improve formatting. 

git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@1173782 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Milosz Tylenda 2011-09-21 18:28:02 +00:00
parent fe7e359367
commit a381632d14
2 changed files with 28 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
openjpa-project/src/doc/manual/migration_considerations.xml
View File

@ -408,7 +408,7 @@
</section>
<section id="jpa_2.2_metamodelArrays">
<title>
MetaModel attributes for Arrays
MetaModel Attributes for Arrays
</title>
<!-- See OPENJPA-2025 for details. -->
<para>
@ -417,7 +417,7 @@
so that arrays which are not stored as PersistentCollections will use a SingularAttribute instead of a ListAttribute.
</para>
<para>
If youre application uses the MetaModel API and your entities contain arrays of any of the following types: byte[], Byte[], char[], Character[] and
If your application uses the MetaModel API and your entities contain arrays of any of the following types: byte[], Byte[], char[], Character[] and
do not use the @PersistentCollection annotation with those fields you will need to update your application to use OpenJPA 2.2.0.
</para>
<para> In order for the existing applications to work with OpenJPA you may:
@ -446,15 +446,15 @@
</section>
<section id="UseNativeSequenceCache">
<title>
useNativeSequenceCache property.
useNativeSequenceCache Property.
</title>
<!-- See OPENJPA-1376 for details. -->
<para>
In the OpenJPA 2.2.x release, code was added which changed the way sequences were generated, please see
In OpenJPA 2.2.0, code was added which changed the way sequences were generated, please see
<xref linkend="jpa_2.2_allocationSize"/> for details. This functionality was eventually back ported
to previous releases, and enabeld by the useNativeSequenceCache property on the DBDictionary. Setting this property
has no effect in 2.2.x and later releases and any occurrence of it should be removed. If previous behavior is
desired (i.e. useNativeSequenceCache=true), please see the details described in section
to previous releases, and enabled by the <literal>useNativeSequenceCache</literal> property on the DBDictionary. Setting this property
has no effect in 2.2.0 and later releases and any occurrence of it should be removed. If previous behavior is
desired (i.e. <literal>useNativeSequenceCache=true</literal>), please see the details described in section
<xref linkend="jpa_2.2_allocationSize"/>.
</para>
</section>

42
openjpa-project/src/doc/manual/ref_guide_dbsetup.xml
View File

@ -3409,27 +3409,6 @@ ResultSet.getString</methodname> will be used to obtain clob data rather than
<methodname>ResultSet.getCharacterStream</methodname>.
</para>
</listitem>
<listitem id="DBDictionary.UseSchemaName">
<para>
<indexterm>
<primary>
schema
</primary>
<secondary>
UseSchemaName
</secondary>
</indexterm>
<literal>UseNativeSequenceCache</literal>: This property was used in
2.1.x and prior releases to indicate (when set to false) that OpenJPA
should not use the CACHE clause when getting a native sequence; instead
the INCREMENT BY clause gets its value equal to the allocationSize
property. Post 2.1.x, code was added to allow said functionality by
default (see OPENJPA-1376).
For forward compatibility, this property still remains, however it has
been deprecated and will eventually be removed. Setting this property
has no effect and any occurrence of it should be removed.
</para>
</listitem>
<listitem id="DBDictionary.UseNativeSequenceCache">
<para>
<indexterm>
@ -3440,6 +3419,27 @@ has no effect and any occurrence of it should be removed.
UseNativeSequenceCache
</secondary>
</indexterm>
<literal>UseNativeSequenceCache</literal>: This property was introduced in
the 2.1.2 release to indicate (when set to <literal>false</literal>) that OpenJPA
should not use the <literal>CACHE</literal> clause when creating a native sequence; instead
the <literal>INCREMENT BY</literal> clause gets its value equal to the allocationSize
property. In the 2.2.0 release, code was added to allow said functionality by
default (see OPENJPA-1376).
For forward compatibility, this property still remains, however it has
been deprecated and will eventually be removed. Setting this property
has no effect and any occurrence of it should be removed.
</para>
</listitem>
<listitem id="DBDictionary.UseSchemaName">
<para>
<indexterm>
<primary>
schema
</primary>
<secondary>
UseSchemaName
</secondary>
</indexterm>
<literal>UseSchemaName</literal>: If <literal>false</literal>, then avoid
including the schema name in table name references. Defaults to <literal>true
</literal>.