Update @updatedAt and now() warning messages to clarify problem only exists in versions before 4.4.0 #6832
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e of @updatedat and now() producing different times only occurs in versions before 4.4.0
aidankmcalister
approved these changes
May 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the prisma-schema-reference documentation "warnings" for the
@updatedAtandnow()attributes to clarify that the problem of the attributes producing different times only exists for versions before 4.4.0Background
The Prisma ORM v4.4.0 release fixed prisma/prisma Issue #12572 with the updates from prisma/prisma-engines PR #3200. So, for Prisma versions v4.4.0 or later, the warnings about
@updatedAtandnow()producing different times do not apply.Related Issues
This PR will resolve prisma/docs Issue #6825