Opened 10 years ago

Last modified 4 years ago

#23027 new New feature

Add database-backend-specific checks

Reported by: Shai Berger Owned by: nobody
Component: Core (System checks) Version: dev
Severity: Normal Keywords:
Cc: Michael Manfre, Ahmad Abdallah Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


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.

Change History (4)

comment:1 by Tim Graham, 10 years ago

Triage Stage: UnreviewedAccepted

comment:2 by Tim Graham, 10 years ago

I haven't looked into details, but I just came across django/db/backends/mysql/ which implements MySQL specific field validation.

comment:3 by Michael Manfre, 10 years ago

Cc: Michael Manfre added

comment:4 by Ahmad Abdallah, 4 years ago

Cc: Ahmad Abdallah added
Note: See TracTickets for help on using tickets.
Back to Top