Opened 14 years ago
Closed 14 years ago
#2847 closed bug (fixed)
mapserverexportplugin bug: layers with same name mix up data/filter statements
| Reported by: | rduivenvoorde | Owned by: | rduivenvoorde |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | Version 1.5.0 |
| Component: | Python plugins and bindings | Version: | |
| Keywords: | Cc: | ||
| Must Fix for Release: | No | Platform: | Debian |
| Platform Version: | Awaiting user input: | no |
Description
see http://lists.osgeo.org/pipermail/qgis-developer/2010-June/010346.html
it appears that 2 postgres layers with the same name, but if one of them has a where-clause applied get both the same FILTER statement in the mapfile
Change History (1)
comment:1 by , 14 years ago
| Component: | Build/Install → Python plugins and bindings |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
fixed in r13844
it appears that it's not a typical postgres problem, but a problem of qgis layers having the same (display)name.
the names were used as keys in a layerlist for map-layer definitions, and used as (non unique!) layer names for the mapfile.
both bugs: because the keys where not unique only the last layer definition was used; and map files generated contained layers with non unique files
both fixed