and this command seems to work
How about I add this command as a temporary wayaround on making this work in github issues
this is exactly it? no additional params?
nope
the --twoWayKey seems to do the job done
removing it makes it fail
i tried all the different permutations with it
ideally two way key shouldnt be passed in a one way relationship but its the thing which is alowing to make it work
interesting ya..
yes
also do note down this observation in github or so, as i just checked both the issues, its not mentioned anywhere
it can be helpful in solving it
btw, the 1st one is the issue related to your problem. and there was a suggestion for using two way key
But that one also creates a relation attribute in another collection
in this one, there is no attribute what so ever in the other collection
Its like exactly the same way as the normal one way relationship is created
no it's the same thing. just with different types
Isnt it that if i create doing same in console, i need to force it for two way and that would create attribute in another collection
Doing this doesnt creates any other attribute and is the exact one way relationship
ya only because the console won't show the key if you don't select two way. this is only for hte workaround
yes, your workaround is a little different
im just saying the problem you're having is the same problem as the 1st issue
in my case i didnt wanted it to create attribute in another collection nothing else
totally agreed
[SOLVED] Unable to create multiple relationship attributes
Recommended threads
- How to Avoid Double Requests in function...
I'm currently using Appwrite's `functions.createExecution` in my project. I want to avoid double requests when multiple actions (like searching or pagination) a...
- Edit ID of an existing collection
Hi there. Is it possible to edit an ID of an existing collection? Right now it looks impossible from AppWrite cloud at least.
- Seed db
hello there... is this correct way to seed appwrite