Bug report #19469
[Processing] "Extract by attribute" algorithm allows an optional value as parameter
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Processing/Core | ||
| Affected QGIS version: | 3.3(master) | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 27297 |
Description
When running the "select by attributes" algorithm without a value filled, you get a warning that there's a wrong or missing value for the value parameter.
In the "Extract by attribute" case, the "Value" parameter is indicated as optional and you can run the algorithm without it, returning a layer with zero feature.
Other than not being consistent with the corresponding "select by..." alg behavior, I fail to see why someone would like to run a conditional algorithm without filling a condition.
Associated revisions
[Processing][Needs-docs] Allow optional "value" in "select by attribute" algorithm
because it's not needed to run null checks (fixes #19469 which is actually reported in the wrong way)
[Processing][Needs-docs] Allow optional "value" in "select by attribute" algorithm
because it's not needed to run null checks (fixes #19469 which is actually reported in the wrong way)
(cherry picked from commit 4e1d29ee241f53297ff2a332554154fd0ad27b73)
History
#1
Updated by Harrissou Santanna about 6 years ago
- % Done changed from 0 to 100
- Status changed from Open to Closed
Applied in changeset qgis|4e1d29ee241f53297ff2a332554154fd0ad27b73.
#2
Updated by Giovanni Manghi about 6 years ago
- Resolution set to fixed/implemented