Maxim
There is a question about relationships in collections.
- I create the "authorId" attribute in the project table and link it to the user table - ok.
- I create the second necessary attribute "inspectorId" by analogy, but I get the error "Attribute with the requested key already exists. Attribute keys must be unique, try again with a different key"
What I expect is that a project can have one author and one inspector, a user can be an author in many projects, the same user can be an inspector in many projects as well
I found information that this is an interface problem and tried through the CLI, but there is exactly the same error. Who can tell me what I'm doing wrong?
TL;DR
Issue with creating relationships in collections - error "Attribute with the requested key already exists" when creating "inspectorId" attribute. Want each project to have one author and one inspector, with users able to be author/inspector in multiple projects. This is likely an interface problem. Solution: Try using a different key for the "inspectorId" attribute. Recommended threads
- 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.
- Migrate from cloud to localhost
Hello everyone. I need to migrate my test project from cloud to localhost, however it seems that this is possible only if a self-hosted appwrite instance it's h...
- Seed db
hello there... is this correct way to seed appwrite