
Hi! I'm testing the realtime in web, and it works flawlessly. I call for an specific ID in the collection, so the document is the only thing I'm subscribing at, but the relationships defined in the DB are not present in that change, nor does it triggers the change when the a related entry gets created or updated. Is this expected? or is there a way to configure this differently? I could not find any docs about this particular topic.
export const subscribe = async (collection: string, document: string) => {
const unsubscribe = await client.subscribe(
`databases.${
DBID as any
}.collections.${collection}.documents.${document}`,
(response) => {
console.log('hello', response);
}
);
return unsubscribe;
};
In the payload Im expecting the object.
{ ...myData, messages (the relationship) }
But only get { ...myData }
Thanks in advance!
Recommended threads
- ❗[Help] Function stuck in "waiting" stat...
Hi Appwrite team 👋 I'm trying to contribute to Appwrite and followed the official setup instructions from the CONTRIBUTING.md guide to run the platform locall...
- Stuck in "deleting"
my parent element have relationship that doesnt exist and its stuck in "deleting", i cant delete it gives me error: Collection with the requested ID could not b...
- Help with 409 Error on Relationship Setu...
I ran into a 409 document_already_exists issue. with AppWrite so I tried to debug. Here's what I've set up: Collection A has 3 attributes and a two-way 1-to-m...
