Changes between Version 13 and Version 14 of FDORfc50

Timestamp:

06/03/10 10:02:15 (15 years ago)

Author:

romicadascalescu

Comment:

--

FDORfc50

@@ -51 +51 @@
 The last option seems to be the best solution since will not enforce other providers to add a blank implementation for those new methods and also will not add a new command. We avoid having two select commands one “extended” and one “join” this way we also eliminate a confusion which might show-up in commands naming. Also it opens a different approach to update a base class without changing all providers to add a blank implementation.
 
+The new methods added on FdoISelect will have a default implementation throwing an exception:
+
+{{{
+  class FdoISelect : public FdoIBaseSelect
+  {
+     /// new added methods
+
+     /// \brief
+     /// Gets the feature class names collection.
+     /// 
+     /// \return
+     /// Returns the collection.
+     /// 
+     FDO_API virtual FdoIdentifierCollection* GetFeatureClassNames()
+     {
+          throw FdoException::Create(FdoException::NLSGetMessage(FDO_NLSID(FDO_3_NOTIMPLEMENTED)));
+     }
+
+     /// \brief
+     /// Gets the join criteria collection.
+     /// 
+     /// \return
+     /// Returns the collection.
+     /// 
+     FDO_API virtual FdoJoinCriteriaCollection* GetJoinCriteria()
+     {
+          throw FdoException::Create(FdoException::NLSGetMessage(FDO_NLSID(FDO_3_NOTIMPLEMENTED)));
+     }
+  }
+}}}
+
 We need to define supported cases and all necessary classes need to be added: