#34242: Behavior of Model.delete() with regards to primary_key fields is not
documented
-------------------------------------+-------------------------------------
Reporter: SwampFalc | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by SwampFalc):
You know, thinking about it some more... What exactly is the reason for
setting the PK to None upon deletion? Is that really necessary?
Should it perhaps only happen when the PK is an autoincrement? Or should
it perhaps not happen at all?
--
Ticket URL: <https://code.djangoproject.com/ticket/34242#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701858179a4b3-7b077fbc-3582-43dc-901e-72d2d27c9cb7-000000%40eu-central-1.amazonses.com.
