#23741: [System Check for migrations] Check presence of all foreign keys
--------------------------------------+------------------------------------
Reporter: notsqrt | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by notsqrt):
Regarding the settings, that's what I did with a local PostgreSQL DB.
I was also wondering how Django does this in their CI platform.
The tricky parts are:
* I have a migrated model, I can check the DB constraints
* I have a new/modified model, the checks must be partial or skipped, but
how to detect this lightly ?
* I am testing the check themselves : if I use a model that does not live
in an app, it won't be present in the DB; otherwise I have to create an
app with models and migrations for my tests, and this seems to be avoid if
possible in django test suite.
I was about to open a pull request, with these questions, so it can be
seen by more people, to get more feedback.
Is it a good idea ?
--
Ticket URL: <https://code.djangoproject.com/ticket/23741#comment:10>
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/065.6bd47bdda9dd883193224eca15b1571f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
