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
- I have try to use the appwrite in to the...
Invalid Origin. Register your new client (oailedjdbkhlkakmnnapoonllbnfmfij) as a new Web (Chrome Extension) platform on your project console dashboard
- what happened with 'never paused' ????
I can already imagine how annoying this is going to be...
- Weird permission failure
when creating an account I use following methods: ``` Future<void> register(String email, String password, String username) async { final user = await accoun...