#5139: Custom primary_key broken when saving
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Component: Database wrapper
Version: SVN | Resolution: wontfix
Keywords: primary_key save | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------+-------------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
Why do you expect this to do anything? If you have a manual pk field, you
have to set it yourself. So it already exists on the model. If you want an
autoincrementing field, use an AutoField, not an Integer Field (and we'll
fill it in for you).
Please reopen if I've overlooked something here, but the behaviour you are
expecting doesn't seem logical.
--
Ticket URL: <http://code.djangoproject.com/ticket/5139#comment:3>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
