If several objects of the same type are deleted at the same time, the recognition of which objects must also be deleted does not work correctly.

The reason for this is that an "inSet" query is executed and the object collection is given as an argument. This query is executed in the open transaction, e.g. to find objects that have not yet been committed.

The query accesses an attribute value of the context object, but does not use the object itself to check whether it is contained in the argument collection, but rather its ObjectKey. Thus the test always fails.

Solution

For simple objects, KnowledgItem is replaced by its ObjectKey in the arguments. This should also be done for KnowledgeItem in collections.

Test

test.com.top_logic.knowledge.service.db2.reference.current.global.TestDeletion