Opened 18 years ago
Last modified 16 years ago
#1818 new enhancement
MAXFEATURES for attribute queries
Reported by: | Owned by: | sdlime | |
---|---|---|---|
Priority: | lowest | Milestone: | 5.6 release |
Component: | MapServer C Library | Version: | 4.8 |
Severity: | minor | Keywords: | |
Cc: |
Description (last modified by )
I feel it would be nice if the MAXFEATURES object worked for attribute queries as well as for spatial queries. If an attribute query were performed with a very generic expression resulting in a large result set (>500 records), then there is a lot of work for MapServer to do. For my purposes, I would like to let users of my web-mapping application know when they've entered a poor attribute query (one with a large result set) and not require MapServer to draw all of the results. I do not believe having this feature in MapServer is a requirement for many people. Therefore this enhancement should be a low priority.
Change History (1)
comment:1 by , 16 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 5.4 release |
Note:
See TracTickets
for help on using tickets.
Will try to revisit for 5.4. It still comes up every once in a while and there are probably other bugs related to it.
Steve