#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 timgraham):
It looks like `AutoField()` and `IntegerField(primary_key=True)` create
the same "integer PRIMARY KEY" type on SQLite, but Django doesn't know to
treat the latter definition as an `AutoField` (and I don't think it should
try to). Other databases (tested with PostgreSQL) with throw the expected
`IntegrityError` for a null value in the `language` column.
We could [https://docs.djangoproject.com/en/dev/ref/databases/ document
the issue] or add a database-specific check when SQLite is in use. Is it
worthwhile?
--
Ticket URL: <https://code.djangoproject.com/ticket/25343#comment:6>
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.73e8a18d6375841e1837ca1f84de38af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
