#30748: Abstract model class specifies foreign key – MySQL doesn't have it.
-------------------------------------+-------------------------------------
Reporter: Mike Robinson | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | worksforme
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 Mike Robinson):
I will attempt to produce the simplest possible test case and report back.
However, this issue occurs ''within the Django Admin'' when attempting to
delete a **User**. The table n question is the user-profile as shown
above.
But also: I think that I am seeing other instances of this in the same
application – other cases involving foreign keys and deletion. (Delete
posts, etc.) Yes, it is possible that this is some obscure application
(model) issue and I will indeed pursue this to try to help resolve the
problem. But I am suspicious, specifically, of some issue in
**OneToOneField.**
--
Ticket URL: <https://code.djangoproject.com/ticket/30748#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.ca7f864339b836bce0bacbac2c672af7%40djangoproject.com.
