Changes between Version 2 and Version 3 of FdoDataValueTypeConversion

Timestamp:

10/17/07 15:17:11 (17 years ago)

Author:

gregboone

Comment:

--

FdoDataValueTypeConversion

@@ -2 +2 @@
 == FDO !DataValue Type Conversions ==
 
-== Overview ==
+=== Overview ===
 
 There are a number of places in core FDO and Provider source code where data values are converted from one type to another. These data values include property values for features and property constraint values. Also, as various FDO client applications are written, some of them may also need to do data type conversion.  
@@ -104 +104 @@
  );
 }}}
+
+where:
+
+dataType – specifies the destination type. This parameter is only specified for FdoDataValue::Create(). For the other functions, the destination type is determined by the return type. 
+
+src – specifies the source type and value. It is converted to an !FdoDataValue of the destination type.
+
+shift – determines what happens if conversion would cause the value to change. This can happen when converting between numeric types and the destination type does not have enough precision to hold the value as is (e.g convert 1.9 from Double to Int32 ). Applicable only when both source and destination types are one of Byte, Decimal, Double, Int16, Int32, Int64 or Single:
+
+      true: shift the value by rounding it to the precision allowed by the destination type[[br]]
+      false: throw an exception[[br]]
+
+
+truncate – determines what happens if the value is outside the valid range for the destination type  (e.g. convert 1000000 from !FdoInt32Value to !FdoInt16Value). Applicable only when both source and destination types are one of Boolean, Byte, Decimal, Double, Int16, Int32, Int64 or Single:
+
+      true: truncate the value to:
+              the maximum value for the destination type if the input value is greater than the maximum value[[br]]
+              the minimum value for the destination type if the input value is less than the minimum value[[br]]
+      false: throw an exception[[br]]
+
+When the source type is numeric and the destination type is Boolean, the behaviour differs from the above and is as follows:
+
+      true: convert 0 to false and other values to true[[br]]
+      false: convert 0 to false and 1 to true. Throw an exception for other values[[br]]
+
+
+nullIfIncompatible – determines what happens if the source and destination types are incompatible (e.g. pass !FdoDataTimeValue as src to FdoBoolean::Create()):
+
+      true: returns a null !FdoDataValue (FdoDataValue::!IsNull() = true)[[br]]
+             Note that the pointer returned is not null, the !FdoDataValue returned has its null flag set[[br]]
+
+      false: throw an exception.
+
+See the chart in the attached document for information on which pairs of types are compatible and which are incompatible.
+
+There are no new functions for converting from other types to Strings. This can already be done by the FdoDataValue::!ToString() function.
+
+==== Supporting Functions ====
+
+The following function will be added:
+
+{{{
+FDO_API FdoInt64 FdoStringP::ToInt64()
+}}}
+
+which converts a string to int64 value, and
+
+{{{
+FDO_API FdoStringP::FdoStringP( FdoInt64 value )
+}}}
+ 
+to convert an int64 to string. These functions hide the Win32 and Linux specific differences in doing these conversions.
+