Bug report #18457

Relationship one_to_many

Added by Alessandro Della Libera over 2 years ago. Updated over 2 years ago.

Status:Open
Priority:Normal
Assignee:Matthias Kuhn
Category:Relations
Affected QGIS version:3.0.0 Regression?:No
Operating System:Windows 10 Easy fix?:No
Pull Request or Patch supplied:No Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:26345

Description

QGiS3 doesn' t correctly recognize the 1_N relations between two tables without geographical characteristics, set in the project properties. The form of visualization and change data doesn't correctly visualize the data.
In version 2.8.16 this has correctly been done. Even if you save a working project version 2.18.16 in version 3, it loses the characteristics and the form doesn't display the data of the child table.
Regards
Alessandro

1_many_relations.png - V3_relationsDef (18.3 KB) Alessandro Della Libera, 2018-03-16 10:17 AM

1_many_form_error.png - V3_formError (28.9 KB) Alessandro Della Libera, 2018-03-16 10:17 AM

1_many_relations_v2-18-16.png - v2_relationDef (19.5 KB) Alessandro Della Libera, 2018-03-16 10:17 AM

paths.sql - SQL to create tables with one to many relationship (904 Bytes) Etiënne Thomassen, 2018-03-27 09:52 AM

qgis2_18_17.PNG - Screenshot of attribute form in 2.18 (102 KB) Etiënne Thomassen, 2018-03-27 09:52 AM

qgis3_0_1.PNG - Screenshot of attribute form in 3.0 (79.2 KB) Etiënne Thomassen, 2018-03-27 09:52 AM

History

#1 Updated by Etiënne Thomassen over 2 years ago

I have the same problem, but with one table with geometries. I am using Postgis and have included the SQL to create the tables.
QGIS 3.0 does auto-discover the relationships (great new feature!), but the form to edit the attibutes of the children within the parents window is not there.

In QGIS 2.18 I get the form I expect (added screenshot), with qgis 3.0 I do not (added sceenshot, similar to Alessandro's)

#2 Updated by Michal Jurewicz over 2 years ago

On MacOS is the same problem.

#3 Updated by Gerhard Spieles over 2 years ago

it is a duplicate from #17525

#4 Updated by nagi hekmati over 2 years ago

in qgis 3 :
i have this problem too
my layer and table are stored in postgis
this feature had worked well in prev version
because of importance of this feature thanks for soon correction

Also available in: Atom PDF