FK Violation on -- {1}

[signedav]

-- {1} is not detected as composition (strength) what leads to fk violation when deleting the parent.

[signedav]

While Model Baker handles strength -> Composition -> CASCADE (in QGIS a warning message appears)
So Model Baker could handle this as well as -> Composition -> CASCADE (only confusing thing here is that the children will be duplicated as well)...

Btw. CASCADE is not given with ili2db: ili2db does not create a CASCADE on a composition-fk neither. Why? Maybe because the user could prefer an error message over a cascade delete...