Context Navigation

Changes between Initial Version and Version 1 of Ticket #34207, comment 3

-              initial
+              v1
 Could you elaborate on that? From what I can read none of the examples you linked suggest that `add` supports this feature?
 There is effectively a section that points at the fact that `remove(related)` will remove all entries matching the `(from, to)` tuple but defined by the many-to-many
+There is effectively a section that points at the fact that `remove(related)` will remove all entries matching the `(from, to)` tuple but defined by the many-to-many but I don't see how that demonstrates that your reported use case should be supported.
 In the example you've just provided you don't use `members.add` to add the second relationship to Ringo but rely on explicit `Membership` creation which is supported.
 …
 If you want to enforce the unique existence of a tuple that is a superset of the the `(from, to)` relationship you should use `get_or_create` instead of expecting `add(through_defaults)` to figure out which of your unique constraints should be enforced based on your provided `through_defaults`.
+{{{#!python
+StatementLocation.objects.get_or_create(
+    section=sect,
+    statement=statement,
+    sl_version=new_version,
+)
+}}}