[Qgis-user] Relation (1-N) Unpredictable Result (with default options)

Jeffrey Durrence jeffrey.durrence at mcleanengineering.com
Mon Sep 14 19:32:52 PDT 2020


Today I was trying to set up an edit form for a spatial table with a related, non-spatial table. I have done this many times in the past, but it's been a while. After using Project Properties to set up my relation, I made several attempts to add a new record in the "child" table. Each time I tried, the new record did not get the correct value for the field which relates the two tables. Existing records were displayed as expected and could be edited, but I could not add new features. 

I went to the docs to see if something had changed that might be affecting me. I downloaded sample shapefile data and used that to demonstrate that related records could be created with that data. I set up a clean database and QGIS project file and made several attempts with my PostGIS data. I did observe that some new options were available to me under the widget area of the child table. What had me confused was that with the default options selected (the way I used to do it), the "reference field" values generated for the "new" child records were real values -- just not at all the correct values. 

I tried several things with the PostGIS data, but what finally fixed the behavior for me was to make one change in the default Widget settings for the "reference field" in the child table properties. In my case, enabling the option to "Use a read-only line edit instead of a combobox" resolved the issue. When that is enabled, new child records get the correct value for the reference field. I don't completely understand what determined the inserted values when this option was not enabled, but I would think that enabling this by default would save a lot of confusion for users like me. I was quite surprised that I could not find folks talking about this in the usual places. Could be that there is something local to my environment, but I thought it worth mentioning should someone else stumble upon it. 

Using QGIS LTS (3.10.5) on Ubuntu 20.4 and Windows 10 64-Bit with PostGIS backend (observed same behavior with Postgres 10.14 / PostGIS 2.4.4 and Postgres 12.4 / PostGIS 3.0.0) 

-- 
Jeffrey Durrence 
jeffrey.durrence at mcleanengineering.com 
McLean Engineering Company 
815 South Main Street 
Moultrie, GA 31768 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20200914/ff8dca64/attachment.html>


More information about the Qgis-user mailing list