#26191 closed New feature (needsinfo)
Custom Where Clause when Extra is Deprecated
| Reported by: | Sven R. Kunze | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Change History (2)
comment:1 by , 9 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
comment:2 by , 9 years ago
Wow. Thanks for pointing me at this PR. It seems there is a real effort in making this work.
Haven't tested it but looks quite fully featured once AND and OR are implemented. Until then, I hope extra will continue to function properly.
Note:
See TracTickets
for help on using tickets.
Maybe looking at the pull request that implements full text search in
contrib.postgreswill help you. If you have trouble with the expressions API, please first ask on our support channels, then open a ticket here with the detailed specifics of what exactly cannot be achieved with the new API if that's the case. Thanks!