[Django] #35421: Add support for ParadeDB's pg_search bm25 index in Django

[Django]

#35421: Add support for ParadeDB's pg_search bm25 index in Django
-------------------------------------+-------------------------------------
Reporter: Philippe | Owner: (none)
Noël |
Type: New | Status: new
feature |
Component: | Version:
contrib.postgres |
Severity: Normal | Keywords: postgres search fts
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hi everyone,

I'm one of the makers of ParadeDB. We create the Postgres extension
pg_search (formerly known as pg_bm25), which adds Elasticsearch-level
full-text search to Postgres. You can read more here:
https://github.com/paradedb/paradedb/tree/dev/pg_search

We've seen asked on the Django forums (see here:
https://forum.djangoproject.com/t/elasticsearch-quality-inside-postgresql-
paradedb-introduces-pg-bm25/24654) for support by Django for the pg_search
BM25 index.

I'm not familiar with Django deeply-enough to know where to start, but
we'd love to partner up and build this feature together. Let us know!
--
Ticket URL: <https://code.djangoproject.com/ticket/35421>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#35421: Add support for ParadeDB's pg_search bm25 index in Django
-------------------------------------+-------------------------------------

Reporter: Philippe Noël | Owner: (none)
Type: New feature | Status: closed
Component: contrib.postgres | Version:
Severity: Normal | Resolution: wontfix

Keywords: postgres search fts | Triage Stage:

| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Simon Charette):

* resolution: => wontfix
* status: new => closed

Comment:

Thank you for your report.

I don't think that Django can commit to providing abstractions for all
Postgres extensions out there, the good news though is that it provides a
tons of entry points for custom fields, migration operations, indices, and
lookups to be created.

I'd suggest you look into maintaining your own third-party applications
that provides the adequate abstraction to leverage your commercial
offering. That's what vendors like Cockroachdb and
[https://github.com/pgvector/pgvector-python/tree/master/pgvector/django
other extensions maintainer do].
--
Ticket URL: <https://code.djangoproject.com/ticket/35421#comment:1>