MapGuide RFC 43 - Support Search and Selection on Double Identity Properties
This page contains an change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.
Status
| RFC Template Version | (1.0) |
| Submission Date | December 5, 2007 |
| Last Modified | Trevor Wekel Timestamp |
| Author | Trevor Wekel |
| RFC Status | adopted |
| Implementation Status | implemented |
| Proposed Milestone | 1.2 |
| Assigned PSC guide(s) | Tom Fukushima, Jason Birch |
| Voting History | |
| +1 | Bob, Jason, Tom, Andy, Bruce, Paul |
| +0 | |
| -0 | |
| -1 |
Overview
Add support for Ajax based search and selection when the identity property is a double.
Please note: This RFC is intended for both the 1.2 and 2.0 streams.
Motivation
FDO maps some database types like an Oracle NUMBER(38,0) to an Fdo decimal. The decimal type is a double precision number. MapGuide does not fully support interaction with features based on double precision identity properties. This RFC adds the required API to support this.
Funding/Resources
Autodesk will provide funding and resources.
Proposed Changes
Add the following API to MgSelectionBase
// Add a single selection to the set where the identity property is a double.
void AddFeatureIdDouble(MgLayerBase* layer, CREFSTRING className, double identifier);
Modify the Server and Web Extensions code bases to map the Fdo decimal type to an MgDoubleProperty.
Implications
This is new API only. There will be no effect on existing applications.
MapGuide does not currently support an MgDecimalProperty. Support for an arbitrary precision MgDecimalProperty is beyond the scope of this RFC.
Test Plan
Validate that a feature class with a double precision identity property can be selected and searched upon in the Ajax viewer.
