Ticket #773 (closed Defect: fixed)

Opened 8 years ago

Last modified 8 years ago

Retyping an association definition corrupts DB

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

Description

When an association definition is retyped into a non-association definition type and then retyped back into an association definition the DB is corrupted. The association definition has the cardinality assignments twice. This results in an "Ambiguity Exception" when the server is restarted. A serious problem.

This error exists for a long while, possibly since DM 4.0.

Change History

comment:1 Changed 8 years ago by jri

  • Status changed from new to accepted

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

In 5041b819abd45d751cd3982b812d7d37c389c427/deepamehta:

Core fix: retype association definition (#773).

The DB is not corrupted when an association definition is retyped into a non-association definition type and then retyped back into an association definition.

See #773.

comment:3 Changed 8 years ago by Jörg Richter <jri@…>

In 81972333389adbc15e04530d999028bd76e8e5fa/deepamehta:

Core: restore assoc def cardinality (#773).

If an association definition is retyped into a non-association definition type and then retyped back into an association definition, the cardinality formerly set is restored.

See #773.

comment:4 Changed 8 years ago by jri

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