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
- Realtime api and labels as permission
in my tables i set labels as permission and real-time capabilities stopped working. Before when i was having "any" role everything was working. Note: user have...
- API key not having access to database
My api key with read and write access to row and tables and DB I not working. In my test the results returned an empty database. This is the second time I am...
- How to bypass the rate limit on the back...
Once a month my app has a ton of usage and I always run into the Too many requests 429 error. I am trying to optimize the queues and jobs to manage that, but a...