4 1/2 years this GitHub issue has been sitting after it was acknowledged but now radio silence.
Seems like something worth addressing?
https://github.com/prisma/prisma/issues/5057
GitHub
"Update" on
Json field that preserves the old KV pairs · Issue #5...Hey, when I run an update statement on a table that has a JSON field, I would like to update the JSON field that has some existing data, instead of "replacing" it. What I mean by this is ...
1 Reply
Hey @troop4christ ! I just replied to you on Twitter but I can answer here as well 🙂. Unfortunately, I don’t think we have any updates on this one. We’ve recently revived our public roadmap though, which we will update every three months with the major issues we plan to address. Here’s our first installment: https://github.com/prisma/prisma/issues/25794
We also recently put out the ORM Manifesto which goes into depth on how we want to approach the governance of the ORM. Here’s a link to that: https://github.com/prisma/prisma/discussions/25772
We’re going to continue addressing issues, primarily focusing on those with the most 👍 reactions as it’s the clearest way we have to community need.
I know that’s probably not the answer you want, but does that make sense? Any other questions I can help answer?
GitHub
Prisma ORM Roadmap: Dec 2024 - Feb 2025 · Issue #25794 · prisma/pri...
3 Month Roadmap: Dec, Jan, Feb 1. Maintain a Healthy and Manageable Backlog of Open PRs and Issues Goal: Ensure any one developer can maintain a clear overview of all open PRs and issues. Right now...
GitHub
Prisma ORM Manifesto: Clarity and Collaboration · prisma prisma · D...
Today we published the Prisma ORM Manifesto to mark the start of a new chapter for Prisma. As the project has grown, it’s become increasingly challenging to maintain the repo, stay connected with o...