Same link
post_save
¶
django.db.models.signals.
post_save
¶
Like pre_save
, but sent at the end of the save()
method.
Arguments sent with this signal:
sender
- The model class.
instance
- The actual instance being saved.
created
- A boolean;
True
if a new record was created. raw
- A boolean;
True
if the model is saved exactly as presented (i.e. when loading a fixture). One should not query/modify other records in the database as the database might not be in a consistent state yet. using
- The database alias being used.
update_fields
- The set of fields to update as passed to
Model.save()
, orNone
ifupdate_fields
wasn't passed tosave()
.
On Tue, Jun 27, 2017 at 4:48 PM, yingi keme <yingikeme@gmail.com> wrote:
--Okk.But what i am actually asking is, what type of contents does the **kwargs. Give me a typical example of **kwargs in the context of signals. The actual data **kwargs may contain.
Yingi KemTo view this discussion on the web visit https://groups.google.com/d/https://docs.djangoproject.com/en/1.11/topics/signals/# receiver-functions We'll look at senders a bit later, but right now look at the **kwargs argument. All signals send keyword arguments, and may change those keyword arguments at any time. In the case of request_finished, it's documented as sending no arguments, which means we might be tempted to write our signal handling as my_callback(sender).This would be wrong – in fact, Django will throw an error if you do so. That's because at any point arguments could get added to the signal and your receiver must be able to handle those new arguments.--On Tue, Jun 27, 2017 at 4:14 PM, yingi keme <yingikeme@gmail.com> wrote:So i want to know, when using a model signals. The reciever function has **kwargs. What is the content of **kwargs in this reciever function below:
@reciever(post_save, sender=MyModel)
def func(sender, instance, **kwargs):
# some action.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com .
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users .
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/504e60a9-9ef7 .-4dc6-a1a8-ab734f250455%40goog legroups.com
For more options, visit https://groups.google.com/d/optout .
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com .
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users .msgid/django-users/ .CALn3ei0kP77zFO_ WDPDptZPg7GWOdkyZwtN6sJ9W07d9r uZicg%40mail.gmail.com
For more options, visit https://groups.google.com/d/optout .
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com .
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users .
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/C07282C1- .3DFC-4787-9F52-9C12B07A0AE3% 40gmail.com
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CALn3ei1TdX712FiRx3yk_eAXgHnB8uGR0s2%3DcjHvVbXG9Dy%2BcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment