docs: specify that columns using CreateDateColumn/UpdateDateColumn cannot be set manually #5861
Conversation
This file contains 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
…ot be set manually
liaujianjie
changed the title
|
There are many requests on this feature. I think instead we need to implement this feature to prevent a future confusion. #3271 |
|
I created #5867 . I can close this PR, feel free to update documentation in a different way now. |
|
That's great news, thank you! |
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.
Follows the discussion on #3365.
Columns using the decorators
@CreateDateColumn()and@UpdateDateColumn()cannot have their values manually set. This behaviour is not documented in the docs.This PR documents that behaviour.