Versions Compared

Old Version 7

changes.mady.by.user Keong Lim

Saved on

compared with

New Version 8

changes.mady.by.user Keong Lim

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: rearrange examples, add explanation

...

Documentation

UML diagram for example edge rule

ExampleEquivalent ExampleExplanation
Code Block
languagejs
titleExample Edge Rule
collapsetrue
{
“from”: “tenant”,
“to”: “vserver”,
“label”: “owns”,
“direction”: “OUT”,
“multiplicity”: “One2Many”,
“contains-other-v”: “${direction}”,
“delete-other-v”: “NONE”,
“SVC-INFRA”: “!${direction}”,
“prevent-delete”: “${direction}”
}
Code Block
languagejs
titleEquivalent Example Edge Rule
collapsetrue
{
“from”: “vserver”,
“to”: “tenant”,
“label”: “owns”,
“direction”: “IN”,
“multiplicity”: “Many2One”,
“contains-other-v”: “!${direction}”,
“delete-other-v”: “NONE”,
“SVC-INFRA”: “${direction}”,
“prevent-delete”: “!${direction}”
}
  • tenant "owns" vserver
  • Each "tenant" has one "vserver"
  • Each "vserver" has many "tenants"
  • "tenant" cannot be deleted if related to "vserver"
  • if "vserver" is deleted, nothing is done to "tenant"



General Applicability

  • EdgeRules only apply to "relationship-list" relations in the schema, since the referenced object could be anything
  • EdgeRules do no apply to sub-component relations in the schema, since this is implicit and hard-coded behaviour

...