Back

Best Approach for Updating Related Collections When Client Document Changes

  • 0
  • Self Hosted
  • Databases
  • General
Suiii
16 Aug, 2024, 06:57

I have a Clients collection, and several other collections (ClientFollowUps, ClientHealths, ClientTracks, etc.) that contain a ClientId field referencing the Clients collection. Document security is enabled for all of them.

When creating or updating a Client document, I pass a Permission[] array along with the payload. This same Permission[] is also provided when creating documents in the ClientFollowUps, ClientHealth, and ClientTracks collections, derived from the specific client document.

I realized that whenever a Client document is updated, I also need to update the permissions in all related collections (ClientFollowUps, ClientHealths, ClientTracks, etc.) where the ClientId matches the client being updated.

Technically, it's possible to do this by querying all related documents and updating them whenever the specific client document is updated.

Given your experience and expertise, would you suggest continuing with this approach of updating all related collections whenever the client document is updated, or is there a better way to handle this?

TL;DR
Updating all related collections whenever the client document is updated is a common approach. Alternatively, you can use database triggers or stored procedures to automate this process. Make sure you consider performance implications and data consistency when choosing the best approach.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more