Re: [Django] #13803: Model attribute cannot be named pk and set primary_key=True

4 views
Skip to first unread message

Django

unread,
Jul 31, 2011, 6:04:06 PM7/31/11
to django-...@googlegroups.com
#13803: Model attribute cannot be named pk and set primary_key=True
-------------------------------------+-------------------------------------
Reporter: jonknee | Owner: hjeffrey
Type: Bug | Status: assigned
Milestone: 1.3 | Component: Database layer
Version: SVN | (models, ORM)
Resolution: | Severity: Normal
Triage Stage: Accepted | Keywords: inspectdb
Needs documentation: 0 | Has patch: 1
Patch needs improvement: 1 | Needs tests: 1
UI/UX: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by ramiro):

* keywords: => inspectdb
* ui_ux: => 0


--
Ticket URL: <https://code.djangoproject.com/ticket/13803#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
May 16, 2014, 10:46:03 AM5/16/14
to django-...@googlegroups.com
#13803: Model attribute cannot be named pk and set primary_key=True
-------------------------------------+-------------------------------------
Reporter: jonknee | Owner: hjeffrey
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed

Severity: Normal | Triage Stage: Accepted
Keywords: inspectdb | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by olethanh):

* status: assigned => closed
* resolution: => fixed


Comment:

Looks like this bug was fixed in ee9fcb1672ddf5910ed8c45c37a00f32ebbe2bb1

--
Ticket URL: <https://code.djangoproject.com/ticket/13803#comment:10>

Reply all
Reply to author
Forward
0 new messages