#22741: Migrate fails with `TypeError` when using a callable default for a
`ForeignKey`
-------------------------------------+-------------------------------------
Reporter: rednaw | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: migrations | Triage Stage:
foreignkey | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by reinout):
Yes, it can stay closed.
See #23454, especially comment 5 by Tim:
https://code.djangoproject.com/ticket/23454#comment:5
Basically: yes, it should be an ID. (I assume an instance was OK for
south, which I used previously).
--
Ticket URL: <https://code.djangoproject.com/ticket/22741#comment:4>
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/064.e18b0ad45fac5c35b77671b8832a2fca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
