Hi a error that I see is not so revealing, but I still mention it and it is that in the description of the relationship it is that depending if we see the relationship from the father or children; change the type of relationship in the parent of the image we can see Customer=>To many=> Pizzas and in the son he shows us the opposite Pizzas=>To many=> Customers When the son should show the same Pizzas=>To one=> Customer
also in the child the type of relationship should be shown many to one
Everything looks in order in the code and in the part where Appwrite is actually using the relationship. that mean the even though you see something different the underlying logic still work.
You can open a bug on it,
From what I've seen it seems like this file https://bit.ly/3NxccGk that prints out the relationship don't take in account the
sideof the relationship and just uses the current collection and assuming it's the parent.
correct, the relationship works correct, it is only a description error as I commented
Recommended threads
- function subdomain ssl certs
The generated subdomain isn't getting a valid ssl cert, I was wondering if appwrite automatically generates one or uses a wildcard for *.functions.domain.com? ...
- Whats best practise for Appwrite Cloud?
Appwrite Teams map very nicely to my needs, it is how i group users together. ... I use roles to define permissions. Should I also map a table to each team ? ...
- Error getting preview of file
Rest Response: ``` { "message": "Server Error", "code": 500, "type": "general_unknown", "version": "1.8.1" } ``` Appwrite Logs ``` appwrite ...