#1550 closed defect (fixed)
msQueryByPoint does not always free the resultcache of the pevious query
Reported by: | szekerest | Owned by: | sdlime |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | MapServer C Library | Version: | 4.6 |
Severity: | normal | Keywords: | |
Cc: |
Description
msQueryByPoint does not free the resultcache of the pevious query if the layer is not queryable, therefore the previous results will be reported as the new results. Tamas Szekeres
Change History (4)
comment:2 by , 18 years ago
Status: | new → assigned |
---|
In what situation does a layer go from queryable to not queryable? I'm curious. Note that if this really can be a problem then a couple other of the query function suffer too. Steve
comment:3 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I have made the changes to CVS HEAD, but have not back ported to 4.8 yet. Is necessaru? Marking as fixed.
comment:4 by , 18 years ago
This situation may occur with long running processes like a desktop solution I am working on. Tamas
Note:
See TracTickets
for help on using tickets.