#32367: Problems with 3.2 alpha - primary keys
-------------------------------+--------------------------------------
Reporter: אורי | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.2
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 Simon Charette):
Hello Uri, thanks for testing out the alpha and the report.
> These models should not use auto-created primary keys! I already defined
the primary key in the ancestor of the model. For example class Entity
which class User inherits from. It looks to me like a bug in Django 3.2
alpha.
Could you provide a minimal project with a set of models to reproduce the
issue. I tried the following but couldn't reproduce
{{{#!python
from django.db import models
class Entity(models.Model):
id = models.AutoField(primary_key=True)
class User(models.Model):
pass
}}}
Also neither the `User` or `Entity` models are mentioned in your check
failures above.
--
Ticket URL: <https://code.djangoproject.com/ticket/32367#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/069.7d4e05f24c5434c856aa2384c2ac31e8%40djangoproject.com.
