Context Navigation

Changes between Initial Version and Version 1 of Ticket #27143, comment 2

initial	v1
3	3	Copying the likely fix:
4	4
5		SearchQuery defines its own operators to work around the limitation in Combinable, but fails to take into account that when two SearchQuery instances are combined, you're returned a CombinedExpression (containing SearchQueries). SearchVector does take this into consideration though.The fix would be to define a SearchQueryCombinable Mixin that looks very similar to SearchVectorCombinable, and override the various ~~__or__ and __and__~~ methods, as the SearchQuery type does itself.
	5	SearchQuery defines its own operators to work around the limitation in Combinable, but fails to take into account that when two SearchQuery instances are combined, you're returned a CombinedExpression (containing SearchQueries). SearchVector does take this into consideration though.The fix would be to define a SearchQueryCombinable Mixin that looks very similar to SearchVectorCombinable, and override the various `__or__` and `__and__` methods, as the SearchQuery type does itself.