Guidance on properly cascading deletions
This makes deletion in general more challenging though. You can easily have a scenario where a document’s ID is stored in 1000s or even more other documents. Deleting all of these documents in a single mutation, which is within a single transaction, is simply impossible, as it would require a long-lived transaction, grinding the whole database to a halt (something Convex does not allow, instead failing the mutation).
So in conventional Convex, what's the suggested way to cascade a delete? I would prefer my app to not fail at deleting a workspace only when it has a lot of content in it.
It'd be great to have an example exactly like the ents-saas-starter that doesn't use Ents, but that may be too much to ask.
Thank you,
-Jon
Realtime database for implementing your product with Convex
Team/organization management
Configurable roles and permissions
Member invite emails using Resend
User sign-in and sign-up with Clerk
Website router with Next.js
Slick UX with shadcn/ui


