#34985: Migrations raise AppRegistryNotReady when GeneratedField references
incorrect fields.
-------------------------------------+-------------------------------------
Reporter: Paolo Melchiorre | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: field, database, | Triage Stage: Accepted
generated, output_field |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"101a85a5a06585ba16ecb25860146d034a8a55ec" 101a85a]:
{{{
#!CommitTicketReference repository=""
revision="101a85a5a06585ba16ecb25860146d034a8a55ec"
Fixed #34985 -- Fixed GeneratedFields.contribute_to_class() crash when
apps are not populated.
Thanks Paolo Melchiorre for the report.
Regression in f333e3513e8bdf5ffeb6eeb63021c230082e6f95.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34985#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018bf70ce723-e2ce1a43-35b2-47db-b1b0-83b3546367fc-000000%40eu-central-1.amazonses.com.
