New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON-specific filtering #2444
Comments
Few notes:
Would also just like to mention that as I'm evaluating Prisma as a possibility for our future backend rewrite, this is quite important for us. We have data that is not really viable to store relationally, but still needs to be queryable - and in some cases that dataset could be quite large. If it's helpful at any point, I'm happy to describe more about our use cases for this |
Another thought - it might be nice to have built-in support, or at least a recommended approach, for validating a JSON schema when updating a JSON field |
This feature would be really helpful! For example, we have a column |
Can this please get pushed on the priority list? 🙏 |
+1 This feature would be immensely helpful for me and my team |
really want this feature |
This is really needed and also PostgreSQL supports this naturally with queries. Can we get this soon? |
This is finished and released in 2.23, integration is done. |
JSON Filtering Documentation is also up: https://www.prisma.io/docs/concepts/components/prisma-client/working-with-fields/working-with-json-fields If you run into anything, let us know in #7135! |
Problem
When working with
Json
fields, some databases (like postgres) let you manipulate the JSON value. This is useful for filtering, for example if you want to filter a model with a Json field where one object field (or a specific path) inside the json column matches a provided value. There are other operations like "object contains", "path exists", etc. that would be useful.Additional context
This issue is the prolongation of #2345 - which is about simple filtering by Json field by equality, treating it as a scalar.
The text was updated successfully, but these errors were encountered: