Feature request #17033
Replace provider filter by expression engine
| Status: | Open | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Expressions | ||
| Pull Request or Patch supplied: | No | Resolution: | |
| Easy fix?: | No | Copied to github as #: | 24932 |
Description
Actually layer's filter at provider level is very limited compared to the expression engine and a filtered layer become non-editable which create confusion. A frequently used work-around is to setup a rule-based style to just filter visible features using the common expression engine.
It will be more natural to just replace the provider filter by expression engine if there is no blocking reasons (performance ?).
History
#1
Updated by Harrissou Santanna over 7 years ago
Dominique Lyszczarz wrote:
Actually layer's filter at provider level is very limited compared to the expression engine and a filtered layer become non-editable which create confusion.
I'd just like to add that the edit limitation is related to the data format you are working with (shapefiles?). Database like formats do not suffer from that.
This has to do with, if I recall well what had been answered in the past, some difficulty/impossibility to guarantee features "primary key"... or something like that...
#2
Updated by Dominique Lyszczarz about 6 years ago
Editing filtered layer does not works either with Geopackage, or maybe I'm missing something.
#3
Updated by Giovanni Manghi about 6 years ago
I'd just like to add that the edit limitation is related to the data format you are working with (shapefiles?). Database like formats do not suffer from that.
This has to do with, if I recall well what had been answered in the past, some difficulty/impossibility to guarantee features "primary key"... or something like that...
I also had this perception, but does not seems right see #19529-3 and #18428-3 does not seems a trivial thing to implement/change (edited).