Changes between Version 8 and Version 9 of FDORfc55

Timestamp:

Jan 14, 2011, 2:33:20 PM (13 years ago)

Author:

gregboone

Comment:

--

FDORfc55

@@ -28 +28 @@
 
 The motivation is well explained by:
-Ticket #365 [SHP Provider]: When executing IApplySchema, !Int32 properties are converted to Decimal properties
+Ticket #365 [SHP Provider]: When executing IApplySchema, Int32 properties are converted to Decimal properties
 http://trac.osgeo.org/fdo/ticket/365
 
-      >> If you execute an IApplySchema on a SHP connection. Any Int32 properties in any class definitions inside the schema (to be applied) will be converted to Decimal properties once the schema has been applied. This does not happen if the !Int32 property happens to be an Identity property. <<
+      >> If you execute an IApplySchema on a SHP connection. Any Int32 properties in any class definitions inside the schema (to be applied) will be converted to Decimal properties once the schema has been applied. This does not happen if the Int32 property happens to be an Identity property. <<
 
 For further clarification "will be converted to Decimal properties" refer to !FdoDecimal properties. 
@@ -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) then return an !FdoInt32 rather than an !FdoDecimal. Note SHP doesn't support !FdoInt64 or !FdoInt16 datatypes therefore the mapping to !FdoInt32 is unique.
 
- == Implications ==
+== 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 !FdoInt32 when reading a SHP schema.