If we consider the following example:
Collections:
UserandPostRelationship:Two-way relationshipandone to manyA user can create many posts, but a post belongs to one specific user.
Depending on where we create this relationship, the text seems to be inaccurate on the other side of the relationship. Meaning, if we create this relationship in the User collection, it will sound correct: user can contain many post, post can belong to one user
Having created the relationship in the User collection, if we now look at the relationship in the Post collection it says: post can contain many user, user can belong to one post
Is the text inaccurate or am I missing something? I attached screenshots of this example.
Thanks! it does look like the text isn't right on the child side... π§
would you be able to create a GitHub issue so we don't lose track of it?
Thanks for the reply. Will do. π
Here is the issue: https://github.com/appwrite/appwrite/issues/6016
can you share the screenshots from both attributes in the actual behavior?
Give me a minute
Done, feel free to review quickly and tell me if I should change anything else
perfect!
Recommended threads
- TablesDB `updateRows` returns `database_...
Hi Appwrite team! Iβm seeing a strange issue with TablesDB bulk row updates on a self-hosted Appwrite instance. **Environment** - Appwrite self-hosted `1.9.0` ...
- Update row sheet not loading
After right clicking a row header and click update, the sidebar fails to load (never-ending skeleton)
- DB Relational Table Request
Hi, I'd like to suggest a rewording of the relationships between tables. - Current wording: storeOperatingDays can contain one storeId ...