Opened 16 years ago
Closed 16 years ago
#1130 closed defect (fixed)
Query builder attaches sql clause to wrong entry when PostGIS table has multiple geometry columns
| Reported by: | agnewtj | Owned by: | nobody |
|---|---|---|---|
| Priority: | major: does not work as expected | Milestone: | |
| Component: | Data Provider | Version: | 0.10.0 |
| Keywords: | multiple geometry columns | Cc: | |
| Must Fix for Release: | No | Platform: | Debian |
| Platform Version: | Awaiting user input: | no |
Description
We have a PostGIS table with multiple geometry tables - one polygon and one point. The "Add PostGIS Table(s)" sorts the geometry columns by "Type". So "Point" appears above "Polygon".
When we double click on one of the tables and add selection criteria, the criteria is attached to the geometry column first in the sort sequence. So we have no way to add sql criteria to the "Polygon" column, since the criteria is always attached to "Point".
Note:
See TracTickets
for help on using tickets.
fixed in r8672