From 65d8657f7f07de3b3cc6c6d1ddfb836c2658b23f Mon Sep 17 00:00:00 2001 From: Jannis Leidel Date: Fri, 17 Jun 2011 15:39:42 +0000 Subject: [PATCH] Fixed #15943 -- Documented `raw` argument of pre_save and post_save signals. Thanks, amplivibe. git-svn-id: http://code.djangoproject.com/svn/django/trunk@16432 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/signals.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt index 67476a072f..4e1f7e2967 100644 --- a/docs/ref/signals.txt +++ b/docs/ref/signals.txt @@ -114,6 +114,12 @@ Arguments sent with this signal: ``instance`` The actual instance being saved. +``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. + .. versionadded:: 1.3 ``using`` @@ -139,6 +145,12 @@ Arguments sent with this signal: ``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. + .. versionadded:: 1.3 ``using``