You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2014/02/11 21:13:59 UTC
svn commit: r1567355 -
/isis/site/trunk/content/components/objectstores/jdo/mapping-bigdecimals.md
Author: danhaywood
Date: Tue Feb 11 20:13:58 2014
New Revision: 1567355
URL: http://svn.apache.org/r1567355
Log:
fixing links
Modified:
isis/site/trunk/content/components/objectstores/jdo/mapping-bigdecimals.md
Modified: isis/site/trunk/content/components/objectstores/jdo/mapping-bigdecimals.md
URL: http://svn.apache.org/viewvc/isis/site/trunk/content/components/objectstores/jdo/mapping-bigdecimals.md?rev=1567355&r1=1567354&r2=1567355&view=diff
==============================================================================
--- isis/site/trunk/content/components/objectstores/jdo/mapping-bigdecimals.md (original)
+++ isis/site/trunk/content/components/objectstores/jdo/mapping-bigdecimals.md Tue Feb 11 20:13:58 2014
@@ -1,6 +1,6 @@
Title: Mapping BigDecimals
-Working with `java.math.BigDecimal` properties takes a little care due to scale/precision issues. This is certainly the case for HSQL, and (may be the case ) for all other RDBMS' too.
+Working with `java.math.BigDecimal` properties takes a little care due to scale/precision issues.
For example, suppose we have: