FTS: Full-Text Search API Epic

[matthewmueller]

Problem Statement

Searching for information is one of the most common tasks on the internet. We use Google to search the world-wide web, but many applications also want a more focused search to offer their users.

There are a couple specialized tools for doing full-text search like meilisearch and Algolia, but this is yet another tool you need to setup and manage. Additionally, most of the databases we support have built-in support for full-text search. Since your application likely requires a database, it's often easiest to start with the database's full-text search support.

Unfortunately, Prisma doesn't expose these capabilities yet, so you can't take advantage of the database's built-in support. This issue aims to change that.

Tasks

• FTS: Finalize API Design #7960
• FTS: Seek community feedback #8271
• FTS: Break work down into discrete subtasks #7961
• feat: support full-text search on Postgres prisma-engines#2137
• fix(mariadb): json gt/gte/lt/lte comparisons quaint#315
• FTS: Integrate into the Prisma Client #8694
• FTS: Write integration tests #8695
• Document the Full-Text Search API docs#2137

References

• Community Issue: Full-Text Search Capability #1684
• Internal Design Document

[hugbubby]

O.O

[Jolg42]

Which connectors will support this? (all of them?, it's not clear from the description)

[molebox]

Wait, can we dog food this then and drop algolia?

[Jolg42]

Algolia in docs provides much more than just a full search query though so probably not.
Algolia is much faster for a docs usecase and matches typos and more (analytics, synonyms...).

[jackbravo]

Algolia makes it much more convenient. But both SQLite and PostgreSQL (I guess MySQL too) can match typos, synonyms, and have other features.

[matthewmueller]

@Jolg42, we're focusing on Postgres right now. In the future we'd like to support MySQL and SQLite, but for those databases, we need to define indexes in the Prisma Schema.

@molebox, it would be some work to migrate over but it would be possible!

---

Since these epics are more for our internal planning, I'm going to lock this issue. Please feel free to comment in the original Feature Request issue.

[matthewmueller]

This is now in preview in 2.30.0! Share feedback in this issue: #8877