Opened 13 years ago
Closed 13 years ago
#3347 closed bug (fixed)
Search query should warn when a column does not exist (instead of saying 0 matching features)
Reported by: | Alister | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
Component: | GUI | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | No | Platform: | Windows |
Platform Version: | XP | Awaiting user input: | no |
Description
Using the attribute table's "advanced search" button (or a rule-based rendering filter):
- Type a search query using an attribute column which doesn't exist (e.g. maybe you search for DIAM=150 because you misremembered the name of a column called DIA)
- Click the "test" button
- A message box will say "found 0 matching feature(s)"
It would be better to say "Column 'OBJECTI' does not exist".
Attachments (2)
Change History (3)
by , 13 years ago
Attachment: | bug3347fix.diff added |
---|
by , 13 years ago
Attachment: | patch_for_bug_3347.txt added |
---|
comment:1 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
patch applied in r15175. Thanks Sunil.
Note:
See TracTickets
for help on using tickets.
#3347_fix