
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
- Query.equal error
Hi guys. I'm using Appwrite Cloud, and I'm using version 21 of node-appwrite to benefit from transactions. The problem is I seem to be getting an error when I u...
- Cannot access my Appwrite database on th...
Hello guys, I am currently developing a web app and using appwrite for authentication, database, storage and messaging. It was working well but since yesterday...
- Nuxt Middleware Support
So I'm trying to protect some routes so that the user is redirected back to the login screen should they not have an active session. However, I'm stuck in a lo...
