Feature request #18771
1:n relations: new entries in child layer when child has geometries
| Status: | Open | ||
|---|---|---|---|
| Priority: | High | ||
| Assignee: | - | ||
| Category: | Relations | ||
| Pull Request or Patch supplied: | No | Resolution: | |
| Easy fix?: | No | Copied to github as #: | 26658 |
Description
https://docs.qgis.org/2.18/en/docs/user_manual/working_with_vector/attribute_table.html#id25
If the child layer is a geometryless table then the actual (2.18/3) implementation has no problems.
The example referenced in the manual is about a scenario where the child is a table with geometries, so when the manual says
"The "+" button will add a new feature to the airport layer. And it will assign the new airport to the current region by default." this will effectively add a row in the child table but without the appropriate geometry, because in the relation form the possibility to digitize geometries for new child entries is not implemented.
This leave the data in a inconsistent state and is cause of confusion and data corruption. An similar example bases on geometry postgis tables shows that when saving edits for a new record in the child table, this new record is completely discarded with no message/warning/error whatsoever by QGIS.
History
#1
Updated by Giovanni Manghi over 6 years ago
- Assignee deleted (
Matthias Kuhn)
#2
Updated by Matthias Kuhn over 6 years ago
- Tracker changed from Bug report to Feature request
This would be very nice to have indeed. I am available to work on this.