You'd have to do the insert via an instead of trigger with the appropriate check. It would be a valid enhancement request for Teiid to do this automatically (it has to do something similar to validate security constraints), but it would probably still need some additional metadata to make the check required and default to the current behavior.
Thanks for your quick response?
Create View Parent
Create View Child
FOREIGN KEY (colCHild1)
This is what I have, but the source model does not have any such constraints, it would allow any values for colChild1. I have and Insert instead of trigger. Are you saying this constraint is not sufficient, teiid does not do this automatically and I would need to make the check myself?
Yes, you would need to manually check referential integrity for the relevant insert/update/delete operations on the parent/child.