feat: add case-insensitive support in advanced Json filtering

[lubosmato]

The PR adds case field into Json filtering to allow case-insensitive text filtering with Json fields.

E.g.:

prisma.article.findMany({
  where: {
    title: {
      path: ["en"],
      string_contains: searchText,
      mode: "insensitive",
    },
  }
})

Fixes prisma/prisma#7390

[CLAassistant]

All committers have signed the CLA.

[macrozone]

that would be some awesome to have

[jkomyno]

Thanks for this PR! I've left a couple of comments for further iterations and better compatibility with the other database providers.

[lubosmato]

@jkomyno thank you for review, would you find time for another round?

Also I would like to ask you if you could point me to the right direction. I tried to hook up prisma client with locally built bins/libs to test this feature with prisma generate on an existing project but generated files have no mention of newly added changes (e.g. case field is missing). In dmmf output I can see newly added field case.

I tried to set env vars PRISMA_QUERY_ENGINE_* and PRISMA_SCHEMA_ENGINE_BINARY and run prisma generate. prisma version is showing that correct libs/bins are used but resulting generated types for prisma-client-js generator are not affected.

What needs to be done in order to make prisma-client-js generator generate types with locally built prisma-engines?

[lubosmato]

Hi @jkomyno, what are the next steps/is there anything else that needs to be done from my end?

[codspeed-hq]

CodSpeed Performance Report

Merging #4977 will not alter performance

_{Comparing lubosmato:main (0bfeb01) with main (11f45a2)}

Summary

✅ 11 untouched benchmarks

[aqrln]

Also I would like to ask you if you could point me to the right direction. I tried to hook up prisma client with locally built bins/libs to test this feature with prisma generate on an existing project but generated files have no mention of newly added changes (e.g. case field is missing). In dmmf output I can see newly added field case.

I tried to set env vars PRISMA_QUERY_ENGINE_* and PRISMA_SCHEMA_ENGINE_BINARY and run prisma generate. prisma version is showing that correct libs/bins are used but resulting generated types for prisma-client-js generator are not affected.

What needs to be done in order to make prisma-client-js generator generate types with locally built prisma-engines?

This is slightly annoying to do, sorry for that. Prisma CLI (and generator) doesn't use the query engine to get the DMMF, it uses the WASM module (published as @prisma/prisma-schema-wasm on npm). You can build it locally by running make build-schema-wasm in the engines directory, the built package will be in target/prisma-schema-wasm. Unfortunately there's no convenient way to make CLI use it; what I do is just manually edit https://github.com/prisma/prisma/blob/7955bca6c4e343e452f9138547d42d952ad0c54d/packages/internals/src/wasm.ts#L1 to import this package from the engines directory in the local filesystem and rebuild Prisma.

[lubosmato]

Hi @jkomyno, what needs to be done to finish this?

[lubosmato]

Hi @jkomyno, what needs to be done to finish this?

[lubosmato]

[aqrln]

@lubosmato could you please resolve the conflicts? The changes look good to me.

[lubosmato]

@aqrln thank you for your time! rebased onto main.

[aqrln]

@lubosmato thanks! Would you mind opening a PR to the docs as well? We can also update them ourselves but then this probably won't make it into the next release and will have to go in 6.5.0.

[aqrln]

The dev connections team has confirmed they have time to write docs before tomorrow so no worries about that. I'll go ahead and merge this. Thanks a lot for the contribution!

[platform-kit]

@jkomyno @aqrln Can you confirm that this shipped in 6.5.0? I am running 6.5.0 right now, but a query with the mode: 'insensitive' argument gives the error:

Unknown argument `mode`. Did you mean `lte`? Available options are marked with ?.

Also, FYI it is unclear from the relevant docs page whether this feature is actually available. It both gives instructions on the argument above and says in the FAQs section that it is unavailable.

https://www.prisma.io/docs/orm/prisma-client/special-fields-and-types/working-with-json-fields

[aqrln]

@platform-kit this was shipped in 6.4.0. Please open an issue with a reproduction if it doesn't work for you.