#2207 closed enhancement (wontfix)
[patch] post_add_manipulator_save and post_change_manipulator_save signals
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | normal | Keywords: | dispatcher signal |
| Cc: | rajesh.dhawan@… | Triage Stage: | Unreviewed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This patch adds two new signals: post_add_manipulator_save and post_change_manipulator_save. They are called from the django.db.models.manipulators.AutomaticManipulator save method, after the manipulator fully saves or changes a model and its related objects and files.
Unlike the regular post_save signal, these signals are called after all the related models and FileField/ImageField objects of the models have been fully saved to the database and filesystem. Therefore, these signals can be used to, for example, create thumbnails of ImageFields.
Attachments (1)
Change History (5)
by , 19 years ago
| Attachment: | add_change_manipulators_patch.diff added |
|---|
comment:1 by , 19 years ago
| priority: | normal → low |
|---|---|
| Version: | magic-removal → SVN |
comment:2 by , 19 years ago
| Cc: | added |
|---|
comment:3 by , 19 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Because the automatic manipulators (in their current form) are going away before 1.0, there's no point in adding this to Django.
comment:4 by , 19 years ago
Adrian, that's good news! Is there anywhere I can pick up discussions on these upcoming changes as I am very interested in this area of Django for a couple of my projects? Tried searching on the users and dev group archives before deciding to bother you with this. Thanks.
Add/change manipulator patch