ZBest practice for large, multi-mutation sequence with convex
I'm trying to create a series of mutation calls to handle the event where the user deletes their account.
When a user deletes their account, I need to:
- update every thread the user created (recursive scheduled tasks)
- update every comment the user created (recursive scheduled tasks)
- update user details
- update or delete every message the user created (recursive scheduled tasks)
Given resource limits for each mutation, i'm guessing invoking 4 separate mutations from the client (rather than inside a single parent mutation) is the way to go here...maybe not..
Should one of these mutations fail, I'll either need to rollback the updates and throw an error or ... I need to think of a better way to handle this altogether. I could also be going about this rather inefficiently...hence me bringing this up here, in case im making an incorect assumption about Convex.
When a user deletes their account, I need to:
- update every thread the user created (recursive scheduled tasks)
- update every comment the user created (recursive scheduled tasks)
- update user details
- update or delete every message the user created (recursive scheduled tasks)
Given resource limits for each mutation, i'm guessing invoking 4 separate mutations from the client (rather than inside a single parent mutation) is the way to go here...maybe not..
Should one of these mutations fail, I'll either need to rollback the updates and throw an error or ... I need to think of a better way to handle this altogether. I could also be going about this rather inefficiently...hence me bringing this up here, in case im making an incorect assumption about Convex.
