github/directus
1
1
Fork 0
mirror of https://github.com/directus/directus.git synced 2026-04-25 03:00:53 -04:00
Code Issues Packages Projects Releases Wiki Activity

Correct docs for corresponding field for M2M relationship (#19284)

Browse Source
This commit is contained in:
Pascal Jufer
2023-07-28 16:59:55 +02:00
committed by GitHub
parent 99d1a64553
commit bb59633c2d
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/app/data-model/relationships.md
View File

@@ -260,14 +260,15 @@ Note the following points from the schema above. When we create an M2M in Direct
- Our junction collection, `recipe_ingredients`, each row contains two foreign key columns. This is what creates the
relationships between the two tables.
- Assuming the M2M alias field is created within the `recipes` collection, Directus does not automatically add a field
to display recipes within the `ingredients` collection. However, you can configure an alias field within `ingredients`
if desired:
to display recipes within the `ingredients` collection. However, you can easily add such a field when creating the M2M
field within the `recipes` collection, by clicking on `Continue in Advanced Field Creation Mode`, opening the
`Relationship` tab and selecting `Add M2M to "ingredients"`:
```
ingredients
- id
- name
- recipes (an O2M alias field, does not exist in the database, enables access to all the recipes related to an ingredient)
- recipes (an M2M alias field, does not exist in the database, enables access to all the recipes related to an ingredient)
```
- Notice that the junction collection also has a `quantity` field, which tracks how much of each ingredient is needed