Check correctness object Primary Business key constraint validation - use case insert object by API

InfoWings / Knowledge-Net

Complex data management solution

1 stars 2 forks source link

Check correctness object Primary Business key constraint validation - use case insert object by API #375

Closed samovl closed 5 years ago

sreznick commented 5 years ago

It is not business key violation in stict sense. When object Obj is created on subject Subj, then Subj is deleted, new subject with name Subj is created, then nobody forbids one to create another Obj with new subject names Subj. I looks like correct behaviour for me.

May be it makes sense to discuss it.

@samovl

underlow commented 5 years ago

If we're talking about object dups on cs1 then I did not recreate subject before insertion

underlow commented 5 years ago

Sorry, I did recreated subject. This is not reproduced with same subject. Can be closed.

Although, another one should be opened to highlight/shadow/emphasize somehow "Soft deleted" entities on UI