Fix for @Column on timestamp defined as timestamp(255)#3740
Merged
Conversation
As per #3720 ``` @column ZonedDateTime zonedDateTime2; ``` ... resulting in DDL generated as `timestamp(255)`. This is occurring when the JPA dependency is used like: jakarta.persistence:jakarta.persistence-api:3.2.0 rather than using the transitive dependency that ebean includes. Workaround: Remove the jakarta.persistence:jakarta.persistence-api:3.2.0 dependency. Fix: The fix here is to use a timestamp type that has a maximum precision. When a precision/length is specified greater than the maximum precision then the fallback type is used which is `timestamp` without any 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
... resulting in DDL generated as
timestamp(255).This is occurring when the JPA dependency is used like:
jakarta.persistence:jakarta.persistence-api:3.2.0rather than using the transitive dependency that ebean includes.Workaround:
Remove the jakarta.persistence:jakarta.persistence-api:3.2.0 dependency.
Fix:
The fix here is to use a timestamp type that has a maximum precision. When a precision/length is specified greater than the maximum precision then the fallback type is used which is
timestampwithout any precision.