mirror of https://github.com/apache/openjpa.git
OPENJPA-686 - Commit on behalf of Fay Wang. Updating manual on Sybase specific behavior.
git-svn-id: https://svn.apache.org/repos/asf/openjpa/trunk@684795 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
7432d1e1ef
commit
5396a66b2b
|
@ -1004,6 +1004,19 @@ not part of the declaration of a cursor or which is not inside a stored
|
||||||
procedure.</literal> ".
|
procedure.</literal> ".
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Applications performing update/insert data of the BigDecimal java type may fail
|
||||||
|
with OptimisticException if the data exceeds the scale or precision of the
|
||||||
|
column on Sybase. To avoid this problem, applications can specify the precision
|
||||||
|
and scale for the numeric type by setting numericTypeName='NUMERIC(p,s)' for
|
||||||
|
the column type mapped by the BigDecimal java type. See
|
||||||
|
<link linkend="openjpa.jdbc.DBDictionary">openjpa.jdbc.DBDictionary</link> for
|
||||||
|
more detail. Alternatively, application can set the precision and scale using
|
||||||
|
the standard <classname>Column</classname> annotation, described in
|
||||||
|
<xref linkend="jpa_overview_mapping_column"/>.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</section>
|
</section>
|
||||||
</section>
|
</section>
|
||||||
|
|
Loading…
Reference in New Issue