#23027: Add database-backend-specific checks
------------------------------------------------+------------------------
Reporter: shai | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Different database backends have different features and behaviors. As a
result, some definitions which may be ok on some backends, may warrant
warnings or even errors on other backends.
As one example, a 65-chars-long field name is a problem on PostgreSQL, but
not on any other core backend; as another, column named "timestamp"
warrants a warning on Oracle (it might work or not...) but not anywhere
else.
The place where such definitions are checked is the checks framework; and
to account for the different behaviors, we need database-backend-specific
checks.
This is a spin-off from #13711 -- which, in its last iteration, needed
special care for the field-name-too-long check.
--
Ticket URL: <https://code.djangoproject.com/ticket/23027>
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/047.018147214b135dc7b56112583ac79023%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
