Alternative Fix for @Column on timestamp defined as timestamp(255)#3741
Closed
rbygrave wants to merge 1 commit into
Closed
Alternative Fix for @Column on timestamp defined as timestamp(255)#3741rbygrave wants to merge 1 commit into
rbygrave wants to merge 1 commit into
Conversation
As per #3720 Fix: Detect the default value of `@Column.length()` which will be 255 when the JPA API is used rather than the Ebean supplied one.
Member
Author
|
Closing this PR as another approach was taken which was to make the timestamp type (that does have precision but not 255 worth of precision) more robust in terms of how it handles precision. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As per #3720
Fix:
Detect the default value of
@Column.length()which will be 255 when the JPA API is used rather than the Ebean supplied one.