Changes between Version 42 and Version 43 of FDORfc50

Timestamp:

07/16/10 12:33:19 (14 years ago)

Author:

gregboone

Comment:

--

FDORfc50

@@ -167 +167 @@
       };
 }}}
-In case user will try to use FdoJoinType_None to define a FdoJoinCriteria, an exception will be thrown that's because FdoJoinType_None is added just to define unsupported value for join type.
+In case user will try to use !FdoJoinType_None to define a !FdoJoinCriteria, an exception will be thrown that's because !FdoJoinType_None is added just to define unsupported value for join type.
 
 We need to add two new methods in connection capabilities: supports join selects (to avoid an exception when a user will try to use the new method from FdoISelect) and also supported join types which can be a collection or a value as OR between values, since all join types cannot be more than we can fit in a int32 using OR e.g.: val1|val2. We need to add an extra capability named !SupportsSubSelects() since sub-select will be handled in filter side and applications might need a way to detect if it will allow users to create sub-selects in filter.
-GetJoinTypes() will return FdoJoinType_None in case no join is supported.
-
-Default implementation for GetJoinTypes() will return FdoJoinType_None and SupportsJoins() will return false, since is not normal to throw exceptions when caller wants to get capabilities.
+!GetJoinTypes() will return !FdoJoinType_None in case no join is supported.
+
+Default implementation for !GetJoinTypes() will return !FdoJoinType_None and !SupportsJoins() will return false, since is not normal to throw exceptions when caller wants to get capabilities.
 
 {{{