🐛 Bug Report: Realtime not triggering document updates on parent for removals of association

[ndizazzo]

👟 Reproduction steps

Setup

1. Create two collections: Assembly & Part (or whatever you like)
2. Create a two-way parent-child relationship between the collections. Inside Assembly:
   i. Attribute Key: parts
   ii. Attribute Key (related collection): assembly
   iii. Relation: one-to-many
   iv. Ensure to set the "on delete" behaviour to "Set document id to NULL in all related documents"
3. Write some code using the web SDK to subscribe to the documents channel for the Assembly collection only (databases.*.collections.assembly.documents)

Testing

4. Use createDocument in the SDK to create an Assembly
5. Use updateDocument in the SDK on the Assembly created above to add a new Part document, which creates the association for you
6. Observe that the promise for the Assembly is called (as expected) when the association was created
7. Observe in the Appwrite UI that the documents exist and have the data provided
8. Now, use deleteDocument in the SDK on the Part above, to remove the part and the association from Assembly
9. Observe that the promise for the Assembly is not called
10. Observe in the Appwrite UI that the Part no longer exists and the association in Assembly is gone

👍 Expected behavior

✅ Real-time should send a payload update for Assembly when the association is created
✅ Real-time should send a payload update for Assembly when the association is deleted

👎 Actual Behavior

✅ Real-time should send a payload update for Assembly when the association is created
❌ Real-time should send a payload update for Assembly when the association is deleted

🎲 Appwrite version

Version 1.4.x

💻 Operating system

Linux

🧱 Your Environment

Appwrite is self-hosted with docker-compose in a virual machine on Ubuntu 22.04.

Appwrite Version: 1.4.1
Appwrite SDK: web

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[ndizazzo]

For those who might be searching issues for something similar, a workaround I've devised is to add a Datetime field named touch on the parent object (in this case, Assembly) that I also update to be a new Date() immediately after removing associations.

This isn't ideal, but allows me to receive the updated parent object with the association removed as I'd expect.

[Haimantika]

Thanks @ndizazzo for raising the issue and also posting the work around. Tagging @abnegate to look into this.

[ishmeet5ingh]

is there any solution for this bug?