I'm exploring the relationship feature for a specific scenario. My intention is to utilize it for validating the existence of a parent document.
What exactly is the limitation of this feature? I've managed to create 6 distinct collections – for the sake of explanation, let's call them Col1 to Col6 where Col1 - Col6 all refer to each other in sequence Col1-> Col2 -> Col3 and so on.
A guess from my side is that the max depth of three limitation comes into play when Creating/Reading/Updating documents?
3 levels is correct 😄 Reference: https://discord.com/channels/564160730845151244/1102090629862932531
but why relationship attribute is removed from appwrite cloud?
it's not removed. relationships were introduced in 1.3.x. Cloud is on 1.1.2
[CLOSED] Relationship max depth
[CLOSED] Relationship maximum depth
Recommended threads
- Weird permission failure
when creating an account I use following methods: ``` Future<void> register(String email, String password, String username) async { final user = await accoun...
- Relation Question
How do I create a relation from table y to an others x.$id. in my example I have a users table where I use Appwrites unique User IDs and I want other tables fo...
- Unknown attribute type: varchar / text
Since the `string` type is deprecated I tried using `varchar` and `text` in some newer tables, but when running `appwrite pull tables && appwrite types ./src/li...