-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SingleInheritance views use default obj_id of parent instead of child #65
Comments
This should be the same, subclasses should have the same PK as their superclass.
|
If you add a cover in vw_cover, we use
However, when creating an item with obj_id =NULL, we use |
I see the problem: |
Solve in bugfixing, maybe upstream in pirogue |
Could you add a bit of context? Is it a case when you insert data with QGIS? The QGIS project should be set so that the obj_id get generated right but I'm open to enhancements on that side! |
@cymed Can you show, where this happens in the code? |
It happens in pirogue, called in wastewater/datamodel/app/create_app.py Lines 118 to 126 in 1906fab
in pirogue, I suppose we enter the exception in https://github.com/opengisch/pirogue/blob/9cbf10f2a8811d84b2051b6b1d2a9c2b78b4a4bb/pirogue/single_inheritance.py#L77-L80 but I can't see why |
fixed by #288 for more details, see opengisch/pirogue#34 |
If the Primary Key of a SingleInheritance view (i.e. tww_app.vw_cover) is missing, the insert command from pirogue uses the PK of the parent (i.e. structure_part). It would be more user friendly to use the child's PK.
The text was updated successfully, but these errors were encountered: