From 5396a66b2bead214285ec2b5363edb40838a5556 Mon Sep 17 00:00:00 2001
From: Albert Lee <allee8285@apache.org>
Date: Mon, 11 Aug 2008 16:20:34 +0000
Subject: [PATCH] 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
---
 .../src/doc/manual/supported_databases.xml          | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/openjpa-project/src/doc/manual/supported_databases.xml b/openjpa-project/src/doc/manual/supported_databases.xml
index df362d0bc..a6f00d79d 100644
--- a/openjpa-project/src/doc/manual/supported_databases.xml
+++ b/openjpa-project/src/doc/manual/supported_databases.xml
@@ -1004,6 +1004,19 @@ not part of the declaration of a cursor or which is not inside a stored
 procedure.</literal> ".
                     </para>
                 </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>
         </section>
     </section>