[mapguide-internals] MapGuide RFC 15 - New Query Features API
Jason.Birch at nanaimo.ca
Sat Feb 3 01:28:29 EST 2007
I've been thinking about this a bit.
While cartographically, I hate the idea of inexplicable blue blobs, functionally I have a few use cases for it. One of the major constraints of my Land System -> MG65 gateway is that it can't select records that have too large a spatial extent. This change in behaviour would solve the problem (I think?).
I still don't like the idea, but... I'm generally opposed to adding configuration items where they are unnecessary, and I can live with the effects for the additional functionality :)
From: mapguide-internals-bounces at lists.osgeo.org on behalf of Robert Bray
Sent: Fri 2007-02-02 9:41 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] MapGuide RFC 15 - New Query Features API
There is really no way for the server to know what it is going to run
into prior to executing a query, unless it starts remembering stats per
feature source and class, which would be a truly interesting piece of
work (probably some database theory available on this topic somewhere).
In the meantime, I'd like to figure out how to monkey wrench this one
in. This is default behavior in ArcIMS and apparently that user base
considers this functionality quite useful. So I guess the key questions are:
- Do we really need both the old and new behavior?
- Assuming we need both, what should the default behavior be?
- How is it controlled, by the end user or application developer?
- What should it be called?
More information about the mapguide-internals