#26191: Custom Where Clause when Extra is Deprecated
----------------------------------------------+--------------------
Reporter: srkunze | Owner: nobody
Type: New feature | Status: new
Component: Database layer (models, ORM) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+--------------------
After fixing https://code.djangoproject.com/ticket/26185 for us, what
worries me is that we would have no way of creating a custom where clause
anymore once extra is deprecated.
We use PostgreSQL fulltext search in a customized way. What is the
intended way of handling custom where clauses (and custom joins) in the
future?
What I don't think is practical is a fully featured PostgreSQL fulltext
support because it might be too complex to handle all edge cases.
--
Ticket URL: <https://code.djangoproject.com/ticket/26191>
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/050.951c7a76f87035b4e7a915cdc3872869%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
