[Django] #23027: Add database-backend-specific checks

[Django]

#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.

[Django]

#23027: Add database-backend-specific checks
--------------------------------------+------------------------------------

Reporter: shai | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | 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

--------------------------------------+------------------------------------
Changes (by timo):

* stage: Unreviewed => Accepted

--
Ticket URL: <https://code.djangoproject.com/ticket/23027#comment:1>

[Django]

#23027: Add database-backend-specific checks
--------------------------------------+------------------------------------

Reporter: shai | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | 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 timo):

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

--
Ticket URL: <https://code.djangoproject.com/ticket/23027#comment:2>

[Django]

#23027: Add database-backend-specific checks
--------------------------------------+------------------------------------

Reporter: shai | Owner: nobody
Type: New feature | Status: new
Component: Core (System checks) | 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

--------------------------------------+------------------------------------
Changes (by manfre):

* cc: manfre (added)

--
Ticket URL: <https://code.djangoproject.com/ticket/23027#comment:3>

[Django]

#23027: Add database-backend-specific checks
--------------------------------------+------------------------------------

Reporter: Shai Berger | Owner: nobody

Type: New feature | Status: new
Component: Core (System checks) | 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

--------------------------------------+------------------------------------
Changes (by Ahmad Abdallah):

* cc: Ahmad Abdallah (added)

--
Ticket URL: <https://code.djangoproject.com/ticket/23027#comment:4>