#25343: pk attribute not set when having own primary key
-------------------------------------+-------------------------------------
Reporter: IlianIliev | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by IlianIliev):
The expected behaviour is that the `pk` property to be set to the value of
the primary key.
Because if you do like this
{{{
lang = Language.objects.create(code='x')
lang.pk is None # returns True
lang = Language.objects.get(code='x')
lang.pk is not None # for example 1
}}}
Then you have quite inconsistent behaviour
--
Ticket URL: <https://code.djangoproject.com/ticket/25343#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.84cfd279444f84fd23d9f611db994c90%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
