Changes between Version 2 and Version 3 of FdoDataValueCompare

Timestamp:

10/17/07 15:04:44 (17 years ago)

Author:

gregboone

Comment:

--

FdoDataValueCompare

@@ -67 +67 @@
 };
 }}}
+
+=== Type Compatibility ===
+
+See attached document -- FDO !DataValue Type Compatibility.docx
+
+=== Type Conversions ===
+
+See attached document -- FDO !DataValue Type Compatibility.docx
+
+=== Collation by Data Type ===
+
+This section describes how values of each type will be ordered for comparison purposes.
+
+'''Boolean''': Values will not be ordered. When !FdoBooleanValue::Compare() is passed another !FdoBooleanValue it will return:
+
+                ''!FdoCompareType_Equal'' – if they are equal
+
+                ''!FdoCompareType_Undefined'' – if they are not equal
+
+'''Numeric Types''' ( Byte, Decimal, Double, Int16, Int32, Int64, Single ):  Values will be ordered numerically.
+
+'''!DateTime''': Values will be ordered from earliest to latest.
+
+'''String, CLOB''': Values will be ordered lexically. TBD: Should collation be a default binary one or the one for the current locale?
+
+'''BLOB''': each pair of bytes from the two values will be compared, starting at the first ones, until the first differing pair of bytes is reached. Comparison will be based on the binary values of these differing bytes. If the end of one BLOB is reached before the other one, the longer BLOB will be considered to be greater than the other BLOB.
+
+=== Issues ===
+
+Should string value comparisons be based on current locale?
+