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 multi-tenant db with $permissions ...
I'm setting up a multi-tenant database with RLS enabled. My users my have permissions set for multiple Teams, and as such when they query the database with the ...
- Authentication on custom Websocket Serve...
Hi, I want to use a custom Websocket Server (using Bun) for my application. However I cant really figure out authentication on custom servers. Session cookies ...
- Realtime for files() works almost well, ...
I have been trying to make use of realtime, today (14.03.26) I have pulled all the latest versions of docker images, and sdk available. Whats working: - Conn...