friendly best practices for soft deletion in vanilla convex
Hi all, just curious about this as its coming up in one my projects - I have a SaaS with a similar data model as the convex cloud product (user -> team-> projects)
I remember in convex ENTs there were some nice ergonomics baked in where we could declare a
It's possible there is documentation about this. I'm just curious about recommended best practices. For example, in the convex cloud product, if I delete my personal account, what happens to the references to this user? (maybe a members table join that would then have a foreign key to a user document that no longer exists). Would you recommend adding a
I have webhooks set up in clerk, where clerk users that are deleted are also deleted in convex. It's possible this soft deletion thing should only be implemented for deleting teams or other resources abstracted from a user.
(fun side question: does convex use convex?)
Big thanks.
I remember in convex ENTs there were some nice ergonomics baked in where we could declare a
.deletion("soft") binding to an ent, representing a soft, or scheduled deletion for a row. It's possible there is documentation about this. I'm just curious about recommended best practices. For example, in the convex cloud product, if I delete my personal account, what happens to the references to this user? (maybe a members table join that would then have a foreign key to a user document that no longer exists). Would you recommend adding a
deletionTime or isDeleted property to a row ? And if so, is the juice worth the squeeze implementing a cascading delete for a fairly complex datamodel? What about deleting a team? Maybe these are handled differently based on having to reference later on. I have webhooks set up in clerk, where clerk users that are deleted are also deleted in convex. It's possible this soft deletion thing should only be implemented for deleting teams or other resources abstracted from a user.
(fun side question: does convex use convex?)
Big thanks.
