#23879: We should use test-skipping, not conditional discovery in runtests.py
--------------------------------------+------------------------------------
Reporter: carljm | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: master
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 MarkusH):
The general idea to have some vendor specifics in the migration code base
sounds good. But I have to agree with Carl on the problems that arise from
not loading a migration. I think the skipping of vendor miss-matches
should happen during the actual migrate process. This still allows
dependency resolutions and state changes independent from the vendor.
Moving the vendor part into operations would furthermore give us some
flexibility for advanced database features. E.g. once `contrib.postgres`
got support for views, these views could be generated within the same
migration, one operation could be
`django.contrib.postgres.operations.CreateView` (with a PostgreSQL vendor
marker) while a `RunSQL` operation would run everywhere but on PostgreSQL.
--
Ticket URL: <https://code.djangoproject.com/ticket/23879#comment:9>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.b7822aab03b963a5ea6eae4c1123f852%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
