Developers hand-code updates and deletes across related records
Developers using ORMs and schema-driven backends report having to write separate, case-by-case logic to update or delete associated records, including join records. That logic can be tedious to maintain as relationships change, and client-side cleanup can be interrupted before it finishes. The evidence centers on Sequelize and AWS Amplify users; one related request concerns syncing database records when files are deleted.
For application developers managing related database records. Mentioned from Apr 2018 to Feb 2024 on GitHub and Hacker News.
8 different people described this problem in 4 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.0/10
- Frequency
- 7.9/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I ended up doing this myself with a Lambda subscribed to a DynamoDB stream, where I semi-replicate the relationships between records (the ones defined in the schema with @connection), so that whenever a record gets deleted, all the connected records which should be removed go with it.
I'm doing this client-side at the moment. I just worry that - given enough time - someone will be half-way through cleaning up a n:n relation and they will lose connectivity
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks