Changes between Version 35 and Version 36 of FDORfc50

Timestamp:

06/24/10 17:49:03 (14 years ago)

Author:

gregboone

Comment:

--

FDORfc50

@@ -163 +163 @@
 }}}
 
-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.
+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.
 
 {{{
@@ -265 +265 @@
 === Handle Sub-Selects ===
 
-Below we define a new class to define sub-select used in the new select. In case a provider supports sub-selects the capability SupportsSubSelects() should return true.
+Below we define a new class to define sub-select used in the new select. In case a provider supports sub-selects the capability !SupportsSubSelects() should return true.
 
 {{{