Changes between Version 41 and Version 42 of FDORfc50

Timestamp:

07/15/10 14:01:51 (15 years ago)

Author:

romicadascalescu

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.
 
 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. 
-Since we can detect if a connection can support joins using GetJoinTypes() then SupportsJoins() can be removed or can be implemented as SupportsJoins(){return (GetJoinTypes() != 0);}
+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.
 
 {{{