Opened 14 years ago
Closed 14 years ago
#15086 closed (invalid)
Django 1.2.4 on FreeBSD serious error
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Core (Other) | Version: | 1.2 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Hi, dear!
First of all - thanks a lot for your work!
I have updated django from 1.2.3 (FreeBSD) to 1.2.4 and now I have a serious error (returned to 1.2.3 version)
I have model and when this model save data, post_save signal creates some other models. When I do it in shell like pp = MyModel(....), pp.save() - all fine,
but when I do it in form like MyForm.save() I have a trouble - records are doubled. In 1.2.3 django all worked fine.
If you need more info please let me know.
Best Reagards,
Crow16384
Attachments (1)
Change History (4)
comment:1 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 14 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Many thanks for your attention!
Yes, You are wright, my explanation is not enough.
I did a small sample (in attachment), to show the problem.
After some days and rest ... I understand that problem is in signals.
Running sample you will see, that records could be doubled because one function is connected twice in
signals. I did a stupid example, but the problem exists. It would be very nice to have no possibility
to connect one function twice in one socket (gtk style, if you allow me). Please let me know, I will give you a sample files.
Thanks for your django. It's a game stone.
Best Regards,
crow16384
comment:3 by , 14 years ago
Component: | Forms → Core framework |
---|---|
Resolution: | → invalid |
Status: | reopened → closed |
This is already covered in the docs: http://docs.djangoproject.com/en/dev/topics/signals/#preventing-duplicate-signals
There isn't anywhere near enough detail here to consider this a bug report. You haven't even told us what error you are getting -- just that it is "serious".
Closing invalid; if you want us to take this report seriously, you need to provide a reproducible test case. If you can do so, feel free to reopen.