this might be a bug, and i need someone to tell me if it is, but when i create a many-to-one relation between two collections in a database, it looks properly when looking at the attribute in place where it was created (image 1), but going to the attribute in the other document collection, it maintains the exact same relation, when i believe it should be flipped (image 2)
TL;DR
Issue: Two-way relationships between collections not reflecting correctly.
The developer is facing an issue where a many-to-one relationship between two collections in a database is not displaying correctly in one of the collections. The relationship should be flipped in one of the collections, but it appears to be the same as the original one.
Solution: The developer might need to adjust the relationship settings or mappings to ensure the correct representation of the two-way relationship between the collections.Recommended threads
- Usage of the new Client() and dealing wi...
Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out - To put in perspective of how the app works, we have a Nuxt Ap...
- Increase by operators
I see appwrite have bunch of useful operators for querieng db. One more I would like to suggest is operators like increase the count of a int columns by 1,2.. ...
- createCollection Deprecated