threeohclock / google-app-engine-django

Automatically exported from code.google.com/p/google-app-engine-django
Apache License 2.0
0 stars 0 forks source link

django.db.models.signals don't get trigger for BaseModel #151

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. create a deprived instance of BaseModel
2. hook up post_save signal
3. call save()
4. expect post_save signal to trigger and execute the handler

What is the expected output? What do you see instead?
post_save signal doesn't get triggered.

What version of the product are you using? On what operating system?
django 1.1
mac
helper r100

Please provide any additional information below.
reference to django signal 
http://docs.djangoproject.com/en/dev/topics/signals/#topics-signals

Original issue reported on code.google.com by trung%ph...@gtempaccount.com on 31 Dec 2009 at 11:38

GoogleCodeExporter commented 8 years ago
We don't support django signals at the moment, patches welcomed.

Original comment by m...@google.com on 8 Jun 2010 at 11:59

GoogleCodeExporter commented 8 years ago
I added what seems to be working Model signals for my application, here's the 
patch.

Original comment by sebastie...@gmail.com on 14 Jul 2010 at 8:21

Attachments:

GoogleCodeExporter commented 8 years ago
This patch seems pretty solid; how about someone integrating it?

Original comment by off...@offby1.net on 13 Sep 2010 at 3:43

GoogleCodeExporter commented 8 years ago
on line 32, created will be set to true if a NotSavedException was raised, and 
false if the model was saved successfully.

That seems the exact opposite behaviour to what is documented in Django.

Original comment by m...@google.com on 13 Sep 2010 at 9:48