| Age | Commit message (Collapse) | Author |
|
Thanks Tim Graham for the review.
Backport of 43380e911073beab401a2fdeca0f25001e170dac from master
|
|
Backport of fb5bd38e3b83c7f0d1011de80f922fc34faf740b from master
|
|
|
|
Thanks Tim Graham and Markus Holtermann for review.
|
|
|
|
|
|
|
|
Thanks to Christian von Roques for the report.
|
|
|
|
Thanks Tim Graham for review.
|
|
|
|
Thanks Berker Peksag and Tim Graham for the reviews.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
docs/ref/contrib/postgres/search.txt.
|
|
|
|
|
|
Thanks for Simon Willison for the spot.
|
|
Adds a reasonably feature complete implementation of full text search
using the built in PostgreSQL engine. It uses public APIs from
Expression and Lookup.
With thanks to Tim Graham, Simon Charettes, Josh Smeaton, Mikey Ariel
and many others for their advice and review. Particular thanks also go
to the supporters of the contrib.postgres kickstarter.
|
|
Used the same test and fix as in #25867.
This required initializing base_field in RangeField.__init__,
not when setting the attribute.
|
|
|
|
|
|
|
|
|
|
serialization.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Provide `contained_by` lookups for the equivalent single valued fields
related to the range field types. This acts as the opposite direction to
rangefield__contains.
With thanks to schinckel for the idea and initial tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
contrib.postgres).
|
|
|
|
|
|
|
|
|