Postgres error 42601 occurs when using _relevance parameter

[kodwi]

Bug description

I'm faced with the error when I try to search text containing two words separated by a space. So if the search text doesn't match any data in db, then it works fine, but if there is some matching data - the error occurs.

The error:

ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(PostgresError { code: "42601", message: "syntax error in tsquery: \"first sec\"", severity: "ERROR", detail: None, column: None, hint: None }), transient: false })

The query that I try to send is in prisma information section. It contains _relevance field, and I think the problem is in its handling (without this field the query works as expected in any cases).

How to reproduce

For example, if I send a string kinda first sec, and the db has a record with first second, so it will crash with the db (postgres) error 42601. But if I send first se1 (two words, but there is no data matching this text) or any string containing one word, it will work.

Expected behavior

No response

Prisma information

this._prismaService.country.findMany({
      where: {
        name: {
          contains: searchText,
          mode: 'insensitive',
        },
      },
      orderBy: {
        _relevance: {
          fields: ['name'],
          search: searchText,
          sort: 'desc',
        },
      },
      take: COMMON.COUNTRY_COUNT,
    });

Environment & setup

• OS: Windows 10
• Database: PostgreSQL 15
• Node.js version: 20.11.0

Prisma Version

prisma                  : 5.13.0
@prisma/client          : 5.13.0
Computed binaryTarget   : windows
Operating System        : win32
Architecture            : x64
Node.js                 : v20.11.0
Query Engine (Node-API) : libquery-engine b9a39a7ee606c28e3455d0fd60e78c3ba82b1a2b (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine           : schema-engine-cli b9a39a7ee606c28e3455d0fd60e78c3ba82b1a2b (at node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm             : @prisma/prisma-schema-wasm 5.13.0-23.b9a39a7ee606c28e3455d0fd60e78c3ba82b1a2b
Default Engines Hash    : b9a39a7ee606c28e3455d0fd60e78c3ba82b1a2b
Studio                  : 0.500.0
Preview Features        : fullTextSearch

[SevInf]

Hi @kodwi.
Could you please share your prisma schema? Thank you.

[kodwi]

@SevInf sure

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["fullTextSearch"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Country {
  id     Int    @id @default(autoincrement())
  name   String @unique
  cities City[]
}

model City {
  id        Int        @id @default(autoincrement())
  name      String
  region    String
  countryId Int
  country   Country    @relation(fields: [countryId], references: [id])
  locations Location[]
}

model Location {
  id        String  @id @default(uuid())
  cityId    Int
  city      City    @relation(fields: [cityId], references: [id])
  address   String?
  latitude  Float?
  longitude Float?
}

[coooola]

@kodwi
I faced exactly the same problem than you. If you look for a field with a space and that there is a result for it, I have the same error.
I've came up with this workaround for now: I'm just replacing spaces by comas in the searched terms. You still have the correct results in the right order.

In your example it would do:

this._prismaService.country.findMany({
      where: {
        name: {
          contains: searchText,
          mode: 'insensitive',
        },
      },
      orderBy: {
        _relevance: {
          fields: ['name'],
          search: searchText.split(' ').join(','),
          sort: 'desc',
        },
      },
      take: COMMON.COUNTRY_COUNT,
    });