#32264: Run database checks by default in some scenarios
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: nobody
Johnson |
Type: | Status: new
Cleanup/optimization |
Component: Core (System | Version: 3.1
checks) |
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 Simon Charette):
* stage: Unreviewed => Accepted
Comment:
> Enable --database __all__ to allow specifying all the database aliases
on the command line.
I wonder if we could make `--database` without a value alias to
`--database __all__` instead. Maybe it's not a good idea due as might
cause an issue similar to #31621?
> Make --deploy imply --database __all__ . Since this is normally run
around the same time as migrate, it shouldn't be an issue to connect to
all databases at that point (and was the behaviour of Django <3.1 anyway).
> Make runserver run database checks for all connections. This will help
catch issues in development.
Makes sense to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/32264#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.a79f5cc93d306f06cdb887f48788991f%40djangoproject.com.
