Multi-edit is extremely slow #36863
Comments
gioman
added
Editing
Bug
@rduivenvoorde it is pretty simple, on a remote postgis host (so the problem shows up clearly, mine are on hetzner for example) try multi-edit 5/50/500/5000 features. Thanks for testing the patch, I can't compile at home during the week end. |
|
Yep, the number of features now do not determine the time it takes to shop up the dialog... Wait for this PR to land, but I think this issue can be closed then |
|
adding feedback tag ;-) |
@rduivenvoorde yes I tested the patch and this is fixed. |
|
Just re-opening till the pr is merged :) |
nyalldawson
added a commit
to nyalldawson/QGIS
that referenced
this issue
Feb 8, 2021
field) when the attribute form is opened. This is incredibly expensive, yet only required in a very very small corner case (field is from a joined layer without the upsert on edit capabilities). Refine logic to avoid the scan wherever we can. Fixes qgis#41366 Fixes qgis#36863
nyalldawson
added a commit
to nyalldawson/QGIS
that referenced
this issue
Feb 16, 2021
field) when the attribute form is opened. This is incredibly expensive, yet only required in a very very small corner case (field is from a joined layer without the upsert on edit capabilities). Refine logic to avoid the scan wherever we can. Fixes qgis#41366 Fixes qgis#36863 (cherry picked from commit c661359)
nyalldawson
added a commit
to nyalldawson/QGIS
that referenced
this issue
Feb 19, 2021
field) when the attribute form is opened. This is incredibly expensive, yet only required in a very very small corner case (field is from a joined layer without the upsert on edit capabilities). Refine logic to avoid the scan wherever we can. Fixes qgis#41366 Fixes qgis#36863 (cherry picked from commit c661359)
nyalldawson
added a commit
that referenced
this issue
Feb 19, 2021
field) when the attribute form is opened. This is incredibly expensive, yet only required in a very very small corner case (field is from a joined layer without the upsert on edit capabilities). Refine logic to avoid the scan wherever we can. Fixes #41366 Fixes #36863 (cherry picked from commit c661359)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This bug is particularly visible when using data from a remote (i.e. not local or local network) datasource.
When selecting features (even a few ones, even just one) and clicking on the multi-edit icon, the dialog takes a lot to come up to a point that if (just?) thousands of features are selected then QGIS basically freezes up (maybe not completely, just it does not return to life in a acceptable amount of time).
QGIS master on Linux and Windows.
On local datasources this problem is much less evident.
The text was updated successfully, but these errors were encountered: