Changes between Version 27 and Version 28 of FDORfc33
- Timestamp:
- 04/15/09 12:44:17 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FDORfc33
v27 v28 39 39 In the circumstance that a computed class is generated, the FDO class definition’s !IsComputed property will return true. In that manner, applications are able to distinguish the content of the feature reader responses coming from the providers and tailor their implementations accordingly. In such a situation, some care will also need to be given to the name of the generated schema and classes. At this point there is no standards exist. It would be beneficial if as a result of this RFC, some uniform conventions could be adopted. 40 40 41 So following up on the above discussion providers, that do return feature readers from SQL commands, will need to come up with the appropriate class definition that the feature reader could expose. 42 43 Here are a few general use cases: 41 Providers that do return feature readers from SQL commands will need to come up with the appropriate class definition that the feature reader could expose. Here are a few general use cases that can be used to guide their implementations: 44 42 45 43 - Select is against a table that has an existing class definition and the select returns the same information as defined by the class definition (e.g. select * from roads).