tortoise / tortoise/tortoise-orm
m2m_changed signal django analog
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.6k
- Forks
- 516
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 9
Description
I'm adapting my project from Django to fastapi + tortoise orm.
All the logic is in the signals.
My task is to catch the event of adding an m2m field.
I'm looking for an m2m_changed analog, but I can't find it in tortoise orm signals.
Are there any workarounds?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing Tortoise ORM's relation and signal behavior, then determine whether an m2m_changed equivalent is intended; done would require a clearly scoped supported mechanism or documented workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, fastapi, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100