Entering a non-existing assoc type as Custom Association Type corrupts the DB

[jri]

When editing an assoc def and entering a non-existing assoc type in the "Custom Association Type" field the DB is corrupted. The solution is to ignore invalid input and displaying a warning.

This problem occur only when editing an assoc def (= an association). In contrast when editing a type (= a topic) invalid user input is ignored and a warning is displayed.

Note: you can't create new association types by typing in the "Custom Association Type" field. You can only choose among the existing association types. If you want create another association type use the Create menu first.

Thanks to JuergeN for addressing this issue!

For the original issue, and for hints about repairing a corrupted DB, see #996.

[Jörg Richter <jri@…>]

In 89c1ecc05e3f9c30f0da738d0c059ce1804ace33/deepamehta:

Assoc Def editor: fix Custom Assoc Type (#1003).

When editing an assoc def and entering a non-existing assoc type in the "Custom Association Type" field, the input is ignored and a warning is displayed. The DB is not corrupted.

See #1003.