#34733: m2m_changed signal is unaware if .set() method is being called
-------------------------------------+-------------------------------------
Reporter: Leif Kjos | Owner: Leif Kjos
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Leif Kjos):
Replying to [comment:2 Mariusz Felisiak]:
> Thanks for this ticket, however, signals are the last resort, required
in really rare cases and could probably be avoided in yours. We don't want
to add new features to them. Personally, I'd use a custom intermediate
models, and add this logic to the `.create()` or `.save()` methods.
>
> Please see TicketClosingReasons/UseSupportChannels for ways to get help
with Django usage, where folks can help you in re-designing this
validation.
>
> You can start a discussion on DevelopersMailingList if you don't agree,
where you'll reach a wider audience and see what other think, and
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets follow triaging guidelines with regards to
wontfix tickets.]
Thanks for the response! Will try that.
--
Ticket URL: <https://code.djangoproject.com/ticket/34733#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018988720441-75ffbb67-bae7-4685-bf92-7cc0acf2a191-000000%40eu-central-1.amazonses.com.
