Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ExampleEquivalent Example
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 Edge Rule
collapsetrue
{
“from”: “vserver”,
“to”: “tenant”,
“label”: “owns”,
“direction”: “IN”,
“multiplicity”: “One2Many”,
“contains-other-v”: “${direction}”,
“delete-other-v”: “NONE”,
“SVC-INFRA”: “!${direction}”,
“prevent-delete”: “${direction}”
}
Code Block
languagetext
titleHow to read in/out/direction
collapsetrue
How to read "from"/"to" and "direction":
- the "in" node is "vserver"
- the "out" node is "tenant"

Code Block
languagetext
titleHow to read the label
collapsetrue
How to read the "label":
- ("out" node) "label" ("in" node) i.e. tenant "owns" vserver

Code Block
languagetext
titleHow to read multiplicity
collapsetrue
How to read "multiplicity" of "One2Many":
- ("in" node) cardinality is "one" i.e. Each "tenant" has one "vserver"
- ("out" node) cardinality is "many" i.e. Each "vserver" has many "tenants"

Code Block
languagetext
titleHow to read contains-other-v
collapsetrue
How to read "contains-other-v":
- traversal of ("out" node) includes data for ("in" node) i.e. traversal of "tenant" includes data for "vserver"

Code Block
languagetext
titleHow to read delete-other-v
collapsetrue
How to read "delete-other-v":
- delete of ("out" node) includes does nothing to ("in" node) i.e. delete of "tenant" includes does nothing to "vserver"

Code Block
languagetext
titleHow to read SVC-INFRA
How to read "SVC-INFRA":
- ?

Code Block
languagetext
titleHow to read prevent-delete
collapsetrue
How to read "prevent-delete":
- delete of ("out" node) is prevented when related to ("in" node) i.e. delete of "tenant" is prevented when related to "vserver"


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

...