Changes between Version 24 and Version 25 of FDORfc33

Timestamp:

Apr 15, 2009, 12:31:43 PM (15 years ago)

Author:

gregboone

Comment:

--

FDORfc33

@@ -44 +44 @@
 Therefore, in cases where the resulting columns come from an existing FDO feature table, a provider can return the class definition corresponding to that table. In cases where the columns come from an unknown table, a class definition can be constructed on the fly. By definition, the FDO class definition returned by an feature reader does not necessarily correspond exactly to an existing FDO class even in existing providers. This is due to the fact that it may only contains the properties that were asked for in the Select command, plus additional computed properties. It is perfectly legal to return a constructed class definition, which is only valid for the select that was executed, and not usable for further updates or inserts.
 
+In the circumstance that a computed class is generated, the FDO class definition’s !IsComputed property would return true. In that manner, applications would be able to distinguish the different 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. 
 
-TODO:
+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. 
 
--- Add !IsComputed reference
--- Discuss schema/class name generation
-
-So following up on the above discussion, providers that return feature readers from SQLCommands will need to come up with the appropriate class definition that the feature reader could expose. 
-
-Here are a few use cases:
+Here are a few general use cases:
 
     - 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).
@@ -61 +57 @@
 TODO: 
 
--- Figure out how providers can determine what are input/output paramaters
--- Procedure calls, input/output parameters, etc....
--- Examples
+-- Figure out how providers can determine what are input/output parameters[[BR]]
+-- Procedure calls, input/output parameters, etc....[[BR]]
+-- Examples[[BR]]
 
 == Requirements ==