Change behavior of @updatedAt when upgrading from 5.21.1 to 6.5.0?
Hi,
When upgrading from version 5.21.1 to 6.5.0 I noticed that some of my snapshot tests where failing to a change of order. Digging down I noticed that my records all have the same
updatedAt value in version 5.21.1 and now different values in Prisma 6.5.0.
I found this issue on GitHub: https://github.com/prisma/prisma/issues/22326. Was this basically resolved somehow? Unfortunately me and ChatGPT could not find a relevant commit that changes this behavior.
Any help and advice is much appreciated.
Best,
AmirGitHub
Issues · prisma/prisma
Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB - Issues · prisma/prisma
2 Replies
You chose to debug with a human. They'll tinker with your query soon. If you get curious meanwhile, hop into
#ask-ai for a quick spin!Thank you for linking to the GitHub Issue.
The Issue is till open, so the issue is confirmed and still not resolved yet.
Does the error go away if you downgrade to prisma version 5.21.1?