Ticket #1020 (closed Defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Deleting a parent type fails

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.8.4
Component: DeepaMehta Standard Distribution Version: 4.8.3
Keywords: Cc: dgf, Malte, JuergeN
Complexity: 3 Area:
Module: deepamehta-core

Description

Deleting a parent type fails if it has 3 or more child types.
The exception says there is an ambiguity problem with he "sequence":

Fetching sequence for type "dm4.contacts.person" failed
(java.lang.RuntimeException)
Reason:
Ambiguity: there are 2 related associations (assocId=3834, assocTypeUri="dm4.core.sequence", myRoleTypeUri="dm4.core.predecessor", othersRoleTypeUri="dm4.core.successor", othersAssocTypeUri="null"),
result=[...]

To narrow the problem:
If the parent type has less than 3 child types deleting the parent works properly.
If you delete the assoc defs (associations) manually until less than 3 remain, deleting the parent type works properly then!
The problem exists for a long while (at least since DM 4.6.1)

Change History

comment:1 Changed 5 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 5 years ago by Jörg Richter <jri@…>

In fe72edfe09a04a8f9798db684d167cab2a62d4df/deepamehta:

Core: fix deleting a parent type (#1020).

See #1020.

comment:3 Changed 5 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.