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
- CORS errors in Obsidian custom plugin
Hi, anyone here familiar with obsidian community plugins? In short: it's a local first note app which supports writing your own add-ons / plugin But I keep get...
- > AppwriteException: The requested servi...
When trying to read or write from my database I get the following error: > AppwriteException: The requested service is disabled. You can enable the service from...
- Courtesy limit reset for non-profit migr...
Hi Team! I'm the architect for a 501(c)(3) non-profit project (Aaria's Blue Elephant) and we just hit our Free plan Database Read limit (currently at 164%). Th...