| 1 | | = FDO RFC 35 - Support Data Store level FDO capabilities = |
| | 1 | = FDO RFC 22 - Support Data Store level FDO capabilities = |
| | 2 | |
| | 3 | This page contains an change request (RFC) for the FDO Open Source project. |
| | 4 | More FDO RFCs can be found on the [wiki:FDORfcs RFCs] page. |
| | 5 | |
| | 6 | |
| | 7 | == Status == |
| | 8 | |
| | 9 | ||RFC Template Version||(1.0)|| |
| | 10 | ||Submission Date|| June 08, 2009 || |
| | 11 | ||Last Modified|| Dan Stoica[[Timestamp]]|| |
| | 12 | ||Author||Dan Stoica, Orest Halustchak || |
| | 13 | ||RFC Status||draft|| |
| | 14 | ||Implementation Status||draft|| |
| | 15 | ||Proposed Milestone||3.4.0.0|| |
| | 16 | ||Assigned PSC guide(s)||Greg Boone|| |
| | 17 | ||'''Voting History'''|| || |
| | 18 | ||+1|| || |
| | 19 | ||+0|| || |
| | 20 | ||-0|| || |
| | 21 | ||-1|| || |
| | 22 | |
| | 23 | == Overview == |
| | 24 | |
| | 25 | This RFC is for changing the behavior of GetCapabilitiesX(). |
| | 26 | |
| | 27 | == Motivation == |
| | 28 | |
| | 29 | There are cases where a provider indicates support of a capability that is actually not supported by a data store the provider may connect to. For example, if an Oracle data store is not prepared for locking, this functionality is not supported in that data store although the provider itself is capable of providing the functionality. ODBC also can connect to a variety of sources, each with varying levels of capability. |
| | 30 | |
| | 31 | == Proposed Solution == |
| | 32 | |
| | 33 | Change the behavior of GetCapabilities. On an open connection it will retrieve the exact capabilities, specific for that database. |
| | 34 | On a closed connection the current behavior will be preserved and provider level capaabilities will be returned to the caller. |
| | 35 | |
| | 36 | == Implications == |
| | 37 | |
| | 38 | |
| | 39 | == Test Plan == |
| | 40 | |
| | 41 | |
| | 42 | == Funding/Resources == |
| | 43 | |
| | 44 | Autodesk to provide resources / funding. |
