2 weeks ago
Dear CAP Team,
I would like to inform you an unexpected behaviour we are getting with the deep insert.
In our data model there is a header entity with some child entities defined as compositions. The header unit has an assert.unique annotation for a non-key field.
When we execute a deep insert that violates the assert.unique constraint, the header is not inserted but the child entities are. I would expect child entities would not be created in this situation.
Best regards,
Marc
User | Count |
---|---|
78 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.