OPENJPA-1837: Revert the statement about XML column as the mentioned limitation does exist in that case.

git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@1032316 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Milosz Tylenda 2010-11-07 17:21:35 +00:00
parent 4b19d0fa4a
commit 5d21297cb6

View File

@ -1273,22 +1273,22 @@ openjpa.ConnectionRetainMode: always
Mapping persistent attributes to <link linkend="ref_guide_xmlmapping">XML columns</link> requires
a JDBC 4 compliant driver if XML strings are longer than 4000 bytes, as counted in database.
Otherwise an <literal>ORA-01461: can bind a LONG value only for insert into a LONG column</literal>
error may result. This limitation is removed in Oracle jdbc driver 11.2.0.x.
error may result.
</para>
</listitem>
<listitem>
<para>
If Oracle dictionary property <literal>MaxEmbeddedBlobSize</literal> or
<literal>MaxEmbeddedClobSize</literal> is set to some limit (i.e. not -1) and embedded collection
with blob/clob attribute is used, a
with BLOB/CLOB attribute is used, a
<literal>"org.apache.openjpa.persistence.ArgumentException:
"x.y.z.EmbedOwner.embedCollection&lt;element:class x.y.z.EmbedValue&gt;"
is mapped as embedded, but embedded field
"x.y.z.EmbedOwner.embedCollection.x.y.z.EmbedValue.blob" is not embeddable.
Embedded element/key/value types are limited to simple fields and direct relations to other
persistent types"</literal> error may result. To overcome this limitation, either use jdbc driver
persistent types"</literal> error may result. To overcome this limitation, either use JDBC driver
11.2.0.x.0 (or later version) or set both <literal>MaxEmbeddedBlobSize</literal> and
<literal>MaxEmbeddedClobSize</literal> oracle dictiionary properties to -1.
<literal>MaxEmbeddedClobSize</literal> properties to -1.
</para>
</listitem>
</itemizedlist>