#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):
An initial implementation at https://github.com/NotSqrt/django/compare/fk-
check
It's harder than I thought:
* how to ignore models that have to be migrated ? (in the actual apps, and
in django tests)
* how to use migrations in django test suite if we ignore unmigrated
models ?
* Is there a standard way for django test suite to test against various DB
backends ? SQLite does not support foreign key constraints in the first
place, so it's not interesting to test against a SQLite DB.. (I have not
looked into the details of djangoci)
* Do I really have to check each model in each database ? or is there
something intelligent to do via database routers ?
--
Ticket URL: <https://code.djangoproject.com/ticket/23741#comment:8>
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.9b5a97e2bac9a5ab334e1d12a2f895be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
