Skip to main content

Live demo: django-icv-search

Search the real synced package docs

Every result below comes from a real django-icv-search query against the actual synced README and doc pages for the seven public ICV packages, not sample data.

Backend: PostgreSQL (full-text search) — production would run Meilisearch or PostgreSQL; the Dummy backend is icv-search's in-memory backend, chosen here because this demo runs on SQLite with no external search server.

4 results for “materialised path” in 33ms

django-icv-taxonomy · README

django-icv-taxonomy README

path (from TreeNode) (managed) Materialised path string. depth (from TreeNode) (managed) Zero-based depth in tree

Ranking score: 0.27 Backend: PostgreSQL (full-text search)

django-icv-taxonomy · README

django-icv-taxonomy README

path (from TreeNode) (managed) Materialised path string. depth (from TreeNode) (managed) Zero-based depth in tree

Ranking score: 0.27 Backend: PostgreSQL (full-text search)

django-icv-tree · README

django-icv-tree README

path format, async-safe, zero tenancy coupling. Replaces django-mptt , django-treebeard (materialised path), and django

Ranking score: 0.11 Backend: PostgreSQL (full-text search)

django-icv-tree · README

django-icv-tree README

path format, async-safe, zero tenancy coupling. Replaces django-mptt , django-treebeard (materialised path), and django

Ranking score: 0.11 Backend: PostgreSQL (full-text search)
How this query ran (icv_search.services.search call)
search("searchdemo_docs", 'materialised path', facets=['package', 'section'], highlight_fields=['title', 'body'], show_ranking_score=True, limit=20)

Same-host stays relative, cross-host goes absolute

Both links below are built the same way, a plain url template tag with no host handling. hostmap decides, per call, whether the result stays relative or becomes absolute.