Changes between Version 50 and Version 51 of FDORfc34


Ignore:
Timestamp:
Sep 20, 2009, 8:43:15 PM (15 years ago)
Author:
klain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FDORfc34

    v50 v51  
    730730To make sure that the access by index is easy to use by client applications, this RFC is including an additional requirement on the indexing.
    731731
    732 The index order supported by the reader must be the same as the order of the properties described by the class definition that is returned by the reader. This allows application developers to have a predictable ordering and not have to maintain additional mapping tables at their end.
    733 
    734 The default implementation described above will follow this requirement. Providers that do not implement these new functions natively will not have to change for applications to be able to use the index access. For providers that implement these new functions natively, this index ordering requirement must be used.
     732The index order supported by the feature reader must be the same as the order of the properties described by the class definition that is returned by the feature reader.
     733The index order supported by the data reader must be the same as the order of the properties added to the FdoIBaseSelect::GetPropertyNames().
     734This allows application developers to have a predictable ordering and not have to maintain additional mapping tables at their end.
     735
     736The default feature reader implementation described above will follow this requirement. Providers that do not implement these new functions natively will not have to change for applications to be able to use the index access. For providers that implement these new functions natively, this index ordering requirement must be used.
     737
     738