#36580: Model validation of constraints fails if condition's Q object references
ForeignObject
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner:
| JaeHyuckSa
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution: needsinfo
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by JaeHyuckSa):
Replying to [comment:4 Jacob Walls]:
> I neglected to check a test project, there's a system check preventing
you from getting into this situation that errors on migrate:
>
> {{{
> ERRORS:
> models.OrderLineItem: (models.E012) 'constraints' refers to the
nonexistent field 'user'.
> }}}
>
> So this needs a more realistic test case to find out if there's a usage
of `Q()` supported on 5.2 that is actually breaking here.
Hi Jacob
Is there a way to run the system checks inside the Django source
repository rather than in my own project?
--
Ticket URL: <https://code.djangoproject.com/ticket/36580#comment:5>
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 visit
https://groups.google.com/d/msgid/django-updates/01070198fad303d9-a77dac67-57ee-4939-80f8-6d29e52cabfe-000000%40eu-central-1.amazonses.com.
