#Invalid relationship value
14 messages · Page 1 of 1 (latest)
also got bunch of error when migrating to self host:
"resourceData": [],
"errors": [
"Error occurred while pushing 'auth:rOWvSWBfp4Y9YaJ8hnTmhEHKaeq2' to destination with message: 'User with the requested ID could not be found.'",
"Error occurred while pushing 'auth:W79ok9uqLnc0fzYalDzn7cfU0sT2' to destination with message: 'User with the requested ID could not be found.'",
"Error occurred while pushing 'databases:unique()' to destination with message: '"Fulltext" index is forbidden on array attributes'",
"Error occurred while pushing 'databases:unique()' to destination with message: '"Fulltext" index is forbidden on array attributes'",
"Error occurred while pushing 'databases:unique()' to destination with message: 'Invalid orders param: Value must a valid array no longer than 100 items and Value must be one of (asc, desc)'",
"Error occurred while pushing 'databases:KCeold8QbWxb0CoKATYg' to destination with message: 'Invalid relationship value. Must be either an array of documents or document IDs, NULL given.'",
"Error occurred while pushing 'databases:BrLYMCH3mXCdsIf2hl2d' to destination with message: 'Invalid relationship value. Must be either an array of documents or document IDs, NULL given.'",
Remember that relationship feature is experimental
Looks like you're not specifying new docs when creating a new document that contains relationships?
cc @minor galleon
For 2-3 years lol 😆
Don't use relationships. Discord doesn't have relationships and works fine, right?
Could you show me your schema?
Looks like you are trying to put an index on a relationship.
Then completely remove the relationship from the appwrite cloud
Relationships do work. Just probably not the way you are using them.
However, its stated everywhere that it is a WIP feature.
Then the supabase is better for queries
Hi guys, I have the same problem. I have two collections and I'm trying to establish a many-to-many relationship using a third collection so I can have additional attributes inside the relation collection. I'm used to working with MySQL, so I'm not sure how I could manage this situation without needing an additional table for this many-to-many relationship with attributes. Any ideas about this? Or has anyone managed to resolve the "Invalid relationship value..." error?