Preview feature feedback: insensitiveFilters

[nikolasburk]

Please share your feedback about the preview feature insensitiveFilters that was released in v2.5.0 in this issue.

• If you encounter a bug, please open a bug report in this repo.
• If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue.

If you have any questions, don't hesitate to ask them in the #prisma2 channel in the Prisma Slack.

[timleslie]

This feature is working exactly how I would want it to, thanks! 🙏

[saraveti]

@nikolasburk - As per Preview Feature documentation here , it says that it is only supported for ProstgreSQL.
Is there a plan to support this for MariaDB, in near feature.

[dpetrick]

@saraveti The reason it's only on postgres is that there's no reason to implement it on MySQL-based databases - they're already case insensitive by default in the vast majority of use cases.

[saraveti]

@saraveti The reason it's only on postgres is that there's no reason to implement it on MySQL-based databases - they're already case insensitive by default in the vast majority of use cases.

@dpetrick . Thanks for providing the response. I did verify the case insensitive search with Prisma & MariaDB. Its working. Thanks again.

[heibel]

This works perfect! Am using it with nexus.

...
where: {
  OR: [
    { name: { contains: "{keyword}", mode: QueryMode.Insensitive } },
    { city: { contains: "{keyword}", mode: QueryMode.Insensitive } },
  ],
},

[nikolasburk]

Thank you so much for the feedback everyone!

Thanks to this, we were able to promote case insensitive filters to stable in today's release 🥳

[Noitidart]

Is this possible with json filter?

    prisma.subscription.findMany({
      where: {
        attrs: {
          path: ['customer', 'email'],
          equals: email,
          mode: 'insensitive'
        }