Changes between Version 3 and Version 4 of FDORfc7

Timestamp:

07/30/07 12:24:36 (17 years ago)

Author:

barbarazoladek

Comment:

--

FDORfc7

@@ -22 +22 @@
 == Overview ==
 
-The purpose of this RFC is to enhance the !FdoClassDefinition class by adding new methods !GetIsViewBased() and !SetIsViewBased().
+The purpose of this RFC is to enhance the !FdoClassDefinition class by adding new methods !GetIsVirtual() and !SetIsVirtual().
 
 
 == Motivation ==
 
-The motivation for this RFC is to expose classes based on virtual objects. The significat differenece between classes based on real and virtual objects is that the later do not contain any data themselves. An RDBMS view is an exmaple of the virtual object. It is really an SQL query. An FDO class based on that query exposes data that is contained in other objects referenced in the query. The class schema characterists like property types and constraints tightly depends on the these objects. Data exposed by the class is more dynamic as it can be edited or deleted from the objects that contain it. 
+The motivation for this RFC is to expose classes based on virtual objects. The significat differenece between classes based on real and virtual objects is that the later do not contain any data themselves. Also, a virtual object is not stored in the datastore as a distinct object. An RDBMS view is one exmaple of the virtual object. It is just a named query. An FDO class based on that query exposes data that is contained in other objects referenced in the query. The class schema characterists like property types and constraints tightly depends on the these objects. Data exposed by the class is more dynamic as it can be edited or deleted from the objects that contain it. 
 
-How these classes can be used? Classes based on virtual objects can be used for limiting or restricting access to some data, for analysis where a class exposes data that is combination of many classes joined in certain way with sometimes complex conditions.
+How these classes can be used? Classes based on virtual objects can be used for limiting or restricting access to some data and for analysis where a class exposes data that is combination of many classes joined in certain way with sometimes complex conditions.
 
-Why is it important to distinguish these classes in FDO? These classes virtuality cannot be expressed by any existing methods of !FdoClassdefinition. In fact, their characteristics are somewhat unpredictable and depend on the underlying virtual object definition.
+Why is it important to distinguish these classes in FDO? Because these classes fall into a different category, for the same reasons why in RDBMSs views are distinguished from tables. These classes virtualness cannot be expressed by any existing methods of !FdoClassdefinition. In fact, their characteristics are somewhat unpredictable and depend on the underlying virtual object definition.
 
 == Proposed Solution ==
@@ -44 +44 @@
             ...
             /// \brief
-            /// Gets the value of m_IsViewBased. It is true if a class is based on view; otherwise is false.
+            /// Gets the value of m_IsVirtual. It is true if a class is based on virtual object; otherwise is false.
             /// 
             /// \return
             /// Returns bool
             /// 
-                FDO_API bool GetIsViewBased();
+                FDO_API bool GetIsVirtual();
 
             /// \brief
-            /// Sets the value of m_IsViewBased. It is true if a class is based on view; otherwise is false.
+            /// Sets the value of m_IsVirtual. It is true if a class is based on view; otherwise is false.
             /// This is an internal method that can only be called by providers. Application should not use this method.
             /// 
@@ -58 +58 @@
             /// Returns nothing
             /// 
-                FDO_API void SetIsViewBased( bool value );
+                FDO_API void SetIsVirtual( bool value );
             ...
         
          private:
             ...
-            FdoBoolean  m_isViewBased;
+            FdoBoolean  m_isVirtual;
             ...
        }
 
 }}}
+
+Note that for the providers where the virtual object concept cannot be used, GetISVirtual() will always return ''false''.
+
 == Implications ==