You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using database level default values, Merge Selected Features tool displays this default value in merge row. Also the header column is set to Manual Value. The correct behavior would be to select value of the first feature as in other columns.
This bug occurs at least with GPKG and PostGIS. QGIS form default values do not change the behavior.
Steps to reproduce the issue
To reproduce the bug I prepared a merge.zip containing merge.gpkg which has line layer with two fields "code" and "field2". "code" field has a default value of 1 set at the table level (ALTER TABLE line ADD COLUMN code int default 1).
If Value Map or relation reference is used, the default value is displayed without mapping. Only when user clicks the cell, the mapped value is displayed.
The text was updated successfully, but these errors were encountered:
Joonalai
added
the
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
label
Nov 19, 2024
What is the bug or the crash?
When using database level default values, Merge Selected Features tool displays this default value in merge row. Also the header column is set to Manual Value. The correct behavior would be to select value of the first feature as in other columns.
This bug occurs at least with GPKG and PostGIS. QGIS form default values do not change the behavior.
Steps to reproduce the issue
To reproduce the bug I prepared a merge.zip containing merge.gpkg which has line layer with two fields "code" and "field2". "code" field has a default value of 1 set at the table level (
ALTER TABLE line ADD COLUMN code int default 1
).Versions
Supported QGIS version
New profile
Additional context
If Value Map or relation reference is used, the default value is displayed without mapping. Only when user clicks the cell, the mapped value is displayed.
The text was updated successfully, but these errors were encountered: