Search box

[ionescu77]

Search box

Autocomplete jquery

https://link.medium.com/yCQ3kBtZXeb

[ionescu77]

Amadeus airport api Django autocomplete

https://developers.amadeus.com/blog/django-jquery-ajax-airport-search-autocomplete

[ionescu77]

https://www.geeksforgeeks.org/implement-search-autocomplete-for-input-fields-in-django/

[ionescu77]

With django haystack

https://django-haystack.readthedocs.io/en/master/autocomplete.html

https://itnext.io/elasticsearch-autocomplete-for-django-9dffef1d3afb

[ionescu77]

Crispy form autocomplete

https://gist.github.com/jpic/e4f48295ab419d007826d1ab510a77a2

[ionescu77]

Autocomplete multiple query set

https://www.javaer101.com/en/article/18215116.html

[ionescu77]

https://django-autocomplete-light.readthedocs.io/en/master/tutorial.html

https://link.medium.com/tLdXfju0Xeb

[ionescu77]

UX autocomplete

https://baymard.com/blog/autocomplete-design

[ionescu77]

Postgresql full text seatch

https://news.ycombinator.com/item?id=35697528

https://admcpr.com/postgres-full-text-search-is-better-than-part1/ https://admcpr.com/postgres-full-text-search-is-better-than-part-2/

The example here only covers short text fields like titles — does anyone know if it performant for full body search of long documents? Yes, and if it falls short you can also use the RUM extension if you don't mind the extra index size (can install via package manager or maybe you db provider like supabase has it available) Yes, it works well but there is a limit of 16k words. See this reddit comment thread [0] for more details, but if your documents are anywhere near that big then I'd say Postgres is definitely not the right tool for you. https://www.reddit.com/r/programming/comments/12yhhcg/comment/jhne71q/?utm_source=share&utm_medium=web2x&context=3

djamgo faceted search

PostgreSQL FTS is mostly great - I wrote a tutorial on using it to build faceted search with Django a few years ago: https://simonwillison.net/2017/Oct/5/django-postgresql-faceted-search/

It does have one surprising limitation: it calculates relevance based on just the current row, rather than being able to take statistics across the whole corpus into account.

Most search engines use TF/IDF or BM25 for relevance calculations, which consider the relative common-ness of terms in comparison to the rest of the corpus. PostgreSQL FTS can't do that as far as I know.

SQLite's built-in FTS CAN do relevance calculations like this! Surprising to see a feature as significant as that show up in SQLite but not in PostgreSQL.

[ionescu77]

Adding Full Text Search to Django With django-watson Learn how to supercharge your Django app with full-text search using Django-Watson. Dive deep into Postgres magic and boost search functionality.

https://idiomaticprogrammers.com/post/django-watson-full-text-search-guide/

https://testdriven.io/blog/django-drf-elasticsearch/

https://testdriven.io/blog/deploying-django-to-ecs-with-terraform/