#32770: Add system check for django.contrib.postgres in INSTALLED_APPS when
using
OpClass().
-------------------------------------+-------------------------------------
Reporter: Seth Yastrov | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Bug => New feature
* resolution: => needsinfo
Comment:
> Therefore I'm reopening the issue, and hoping that this check can be
made, as despite this requirement being mentioned in the docs, the current
behavior is quite unintuitive.
It would be really complicated. First of all, we would need to mix-up
logic from a contrib app and the ORM. Secondly `OpClass()` don't need to
be the topmost expression, so the flatten list of expression would be
necessary. Thirdly we don't have similar checks for fields from
`django.contrib.postgres` app which also require including
`'django.contrib.postgres'` in `INSTALLED_APPS`, e.g. `HStoreField`. I
don't think it's worth complexity, however we can reconsider this decision
if someone provides PoC.
--
Ticket URL: <https://code.djangoproject.com/ticket/32770#comment:4>
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/066.fdb222d8c2c9475d2a4a81594975c174%40djangoproject.com.
