From bcc729c5495426483c21e77d9b8edb8476e5a1ad Mon Sep 17 00:00:00 2001 From: zadam Date: Tue, 30 Jul 2019 22:31:47 +0200 Subject: [PATCH] Updated Promoted attributes (markdown) --- Promoted attributes.md => Promoted-attributes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename Promoted attributes.md => Promoted-attributes.md (99%) diff --git a/Promoted attributes.md b/Promoted-attributes.md similarity index 99% rename from Promoted attributes.md rename to Promoted-attributes.md index 466673a..b9e19b1 100644 --- a/Promoted attributes.md +++ b/Promoted-attributes.md @@ -28,4 +28,4 @@ Another example is with parent - child relationship. Again these always occur in Relation definition allows you to specify such "inverse relation" - for the relation you just define you specify which is the inverse relation. Note that in the second example we should have two relation definitions - one for `isParentOf` which defines `isChildOf` as inverse relation and then second relation definition for `isChildOf` which defines `isParentOf` as inverse relation. -What this does internally is that whenever we save a relation which has defined inverse relation, we check that this inverse relation exists on the relation target note. Similarly when we delete relation, we also delete inverse relation on the target note. \ No newline at end of file +What this does internally is that whenever we save a relation which has defined inverse relation, we check that this inverse relation exists on the relation target note. Similarly when we delete relation, we also delete inverse relation on the target note.