Changes between Version 2 and Version 3 of FDORfc23


Ignore:
Timestamp:
Jul 8, 2008, 9:09:47 AM (16 years ago)
Author:
ronnielouie
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FDORfc23

    v2 v3  
    3434== Proposed Solution ==
    3535
    36 To retrieve the feature class names without having incur the cost of a !DescribeSchema, a new command, !EnumerateFeatureClasses, will be added to the API for obtaining a list of feature class names for a given schema.  If schema is not specified, the list will consist of all feature classes in the feature source.
     36To retrieve the feature class names without having to incur the cost of a !DescribeSchema, a new command, !EnumerateFeatureClasses, will be added to the API for obtaining a list of feature class names for a given schema.  If schema is not specified, the list will consist of all feature classes in the feature source.
    3737
    3838{{{
    … …  
    9898    ///
    9999    /// \return
    100     /// Returns nothing
     100    /// Returns boolean value to indicate if the provider supports specifying class names for this command.
    101101    ///
    102     FDO_API virtual void SetFeatureClassNames(FdoStringCollection* value) = 0;
     102    FDO_API virtual bool SetFeatureClassNames(FdoStringCollection* value) = 0;
    103103
    104104}}}
    … …  
    106106The proposed changes will need to be completed for all FDO providers.  Generally speaking, response time for a full !DescribeSchema command is not much of an issue for the file-based FDO providers when compared to the response time for the RDBMS-based FDO providers. 
    107107
    108 The performance gain from using the new EnumerateFeatureClasses command will be most notable for the RDBMS-based FDO providers. The !EnumerateFeatureClasses command will throw a "Not Implemented" exception when executed against non-RDBMS FDO providers.
     108The performance gain from using the new !EnumerateFeatureClasses command will be most notable for the RDBMS-based FDO providers. The !EnumerateFeatureClasses command will throw a "Not Implemented" exception when executed against non-RDBMS FDO providers.  Additional information will be added to the !GetCapabilities response to allow the providers to indicate its support for the new command.  These will default to “false” for all non-RDBMS FDO providers.
    109109
    110 Additional information will be added to the !GetCapabilities response to allow the providers to indicate its support for the new command.  These will default to “false” for all non-RDBMS FDO providers.
    111 
    112 The DescribeSchema command for non-RDBMS FDO providers will return the schema(s) for all the feature classes regardless of the set of classes specified by the SetFeatureClassNames method. 
     110The !DescribeSchema command for non-RDBMS FDO providers will return the schema(s) for all the feature classes regardless of the set of classes specified by the !SetFeatureClassNames method.  !SetFeatureClassNames will return a boolean to provide feedback to the caller for indicating whether the command supports specifying classes as a criteria when executed against a particular provider.
    113111
    114112== Implications ==