You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/backend/relations.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -597,7 +597,7 @@ The logic for this is provided by the package [z3c.relationfield](https://pypi.o
597
597
This package contains the `RelationValue` object and everything needed to define a relation schema, and all the code that is necessary to automatically update the catalog.
598
598
599
599
A `RelationValue` object does not reference all objects directly.
600
-
For the target, it uses an ID that it gets from the `IntId` utility.
600
+
For the target, it uses an ID that it gets from the {term}`IntId` utility.
601
601
This ID allows direct recovery of the object.
602
602
The source object stores it directly.
603
603
@@ -608,7 +608,7 @@ Because of this, the following happens when saving a relation via a form:
608
608
1. The HTML shows some nice representation of selectable objects.
609
609
2. When the user submits the form, selected items are submitted by their UUIDs.
610
610
3. The widget retrieves the original object with the UUID.
611
-
4. Some data manager gets another unique ID from the `IntID` utility.
611
+
4. Some data manager gets another unique ID from the {term}`IntId` utility.
612
612
5. The same data manager creates a `RelationValue` from this ID, and stores this relation value on the source object.
0 commit comments