= FDO RFC 5 -  {{{FdoClassDefinition }}} Change =

This page contains a request for comments document (RFC) for the FDO Open Source project.  
More FDO RFCs can be found on the [wiki:FDORfcs RFCs] page.

== Status == 
 
||RFC Template Version||(1.0)|| 
||Submission Date||Jul 11, 2007||
||Last Modified||Barbara Zoladek [[Timestamp]]||
||Author||Barbara Zoladek||
||RFC Status||draft||
||Implementation Status ||under development||
||Proposed Milestone||3.3||
||Assigned PSC guide(s)||Greg Boone||
||'''Voting History'''||TBD||
||||Mateusz||
||||Frank||
||||Orest||
||||Greg ||
 
== Overview ==

The purpose of this RFC is to add to {{{FdoClassDefinition}}} the methods for setting and getting a flag indicating if the class definition is based on a view.

== Motivation ==

The top level requirements is to distinguish table and view based classes. However, there is no difference in functionality or behaviour between table and view based classes, for the schema designers it is important to know a type of the underlying datastore object. 

== Proposed Solution ==
{{{
class FdoClassDefinition : public FdoSchemaElement
{
...
private:
...
   FdoBoolean	m_isViewBased;

public:
    /// \brief
    /// Gets the value of mIsViewBased. It is true if a class is based on view; otherwise is false.
    /// 
    /// \return
    /// Returns bool
    /// 
	FDO_API bool GetIsViewBased();

    /// \brief
    /// Sets the value of mIsViewBased. It is true if a class is based on view; otherwise is false.
    /// 
    /// \return
    /// Returns nothing
    /// 
	FDO_API void SetIsViewBased( bool value );
}
}}}


== Implications ==

This change will not cause any side-effects, nor will cause any compatibility problems.
== Test Plan ==

FDO test will be expanded for testing these methods.

== Funding/Resources ==

Autodesk to provide resources / funding to update FDO core.