Changes between Version 12 and Version 13 of FDORfc55

Timestamp:

Jun 1, 2011, 1:12:56 PM (13 years ago)

Author:

danstoica

Comment:

--

FDORfc55

@@ -47 +47 @@
     * the DBF to FDO datatype mapping (physical to logical conversion) needs a small refinement. In the case of DECIMAL(precision, scale) check the scale value. When the scale is 0 (zero) and depending on the precision return FdoInt16, FdoInt32 or FdoInt64 rather than an FdoDecimal. Note SHP provider currently does not support FdoInt64 or FdoInt16 datatypes and they have to be added to the schema capabilities.
 
-Below the mapping between FdoIntX datatypes and Decimal precision:
+Below the mapping between FdoIntXX datatypes and Decimal precision:
 
 || Fdo type ||  precision ||                    range                                ||
@@ -58 +58 @@
 == Implications ==
 
-     * In the case of physical DECIMAL(precision, scale) column the corresponding logical FDO property type will be set according to the scale. The caller must expect either a FdoDecimal or a FdoIntX when reading a SHP schema.
+     * In the case of physical DECIMAL(precision, scale) column the corresponding logical FDO property type will be set according to the scale. The caller must expect either a FdoDecimal or a FdoIntXX when reading a SHP schema.
 
-    * This is a behavior change for the SHP provider. Before this change, SHP would return only FdoDecimal for all numerical FDO types. It would never return an FdoIntX except for the identity property (which actually is not stored). 
+    * This is a behavior change for the SHP provider. Before this change, SHP would return only FdoDecimal for all numerical FDO types. It would never return an FdoIntXX except for the identity property (which actually is not stored). 
 
-    * The provider will return a FdoIntX even for properties which originally were DECIMAL(p, 0). This issue can be mitigated by noting the SHP provider already does silent corrections on the fly in certain cases, like truncating the property names when found too long (both on reading and writing).
+    * The provider will return a FdoIntXX even for properties which originally were DECIMAL(p, 0). This issue can be mitigated by noting the SHP provider already does silent corrections on the fly in certain cases, like truncating the property names when found too long (both on reading and writing).
 
 == Test Plan ==