Changes between Version 4 and Version 5 of FDORfc5
- Timestamp:
- 07/17/07 13:05:29 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FDORfc5
v4 v5 24 24 == Overview == 25 25 26 The purpose of this RFC is to add a new property to the class ''FdoFunctionDefinition'' allowing the specification of the function class a given function belongs to. The valid function types will be defined in an enumeration and initially contain values to indicate aggregate, conversion, date, mathematical, numeric and string functions. The enumeration will also include a value to indicate an unknown function class. This function class will represent the default value.26 The purpose of this RFC is to enhance the class ''FdoFunctionDefinition''. This class allows a provider to define a set of supported expression functions. The list of supported expression functions is accessible as part of the expression capabilities that can be retrieved from a connection. 27 27 28 The following shows examples of functions listed with their corresponding function class: 28 The enhancement will add a new property to the class allowing the specification of the function class a given function belongs to. The valid function types will be defined in an enumeration and initially contain values to indicate aggregate, conversion, date, mathematical, numeric and string functions. The enumeration will also include a value to indicate an unknown function class. This function class will represent the default value. 29 30 The enhancement will allow a consumer of the list of supported expression functions to sort them according to their class. This may help in presenting the functions in a user-defined UI as similar functions can be grouped. The following shows examples of functions grouped according to their corresponding function class: 29 31 30 32 AGGREGATE:: … … 46 48 ''Concat'', ''Instr'', ''Lower'', ''Lpad'', ''Ltrim'', ''Upper'' 47 49 50 48 51 The function class will be set via the currently available interfaces (''create'' method). To allow this the interfaces will be enhanced with an optional function class parameter which will be set to the default value. 52 49 53 50 54 == Proposed Solution == … … 135 139 == Implications == 136 140 137 This change will not cause any side-effects, nor any compatibility problems. 141 This change will not cause any side-effects, nor any compatibility problems. No existing provider needs to change unless the provider wants to use the new feature. 138 142 139 143 == Test Plan ==