When I create a two way relationship and select for example one to many ( eg. one survey -> many questions), in the related collection it is created also as one to many (one question -> many surveys).. is this as expected ?
If it's two way then both collections will have a relationship to each other
I think if you did a one to many, the other collection would actually be a many to one, unlike what you have above.
I would have expected that but it looks like this
huh, yea, I can see that in my own project too. Wonder if that's just a typo mistake? I believe it works as you would expect. At least that's my experience.
Thank you, maybe that's the case, and it' just a typo
In this case, would it be possible to create a "child" document in the questions collection and automatically update an existing "parent" document in the surveys collection ? The documentation only shows the other way around
If it's two way I think you can do
databases.createDocument('[DATABASE_ID]', 'Survey', '[DOCUMENT_ID]', {
questions: [...questions]
});
OR
databases.createDocument('[DATABASE_ID]', 'Question', '[DOCUMENT_ID]', {
survey: survey
});
Recommended threads
- Google Auth not working in a React App
Authentication with Google has failed. It redirects back to the signin route in React. Attached screenshots for configuration of Google console and Appwrite Go...
- Bug Report: Crash when trying to createR...
https://github.com/appwrite/sdk-for-android/issues/96 I think the bug is related with this one https://discord.com/channels/564160730845151244/1443887021314539...
- Dokploy docker compose
Hey guys hope y'all doing well, I was wondering if anyone could share a working 1.8.0 docker-compose that works with Dokploy I tried making it but it just does...