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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HHH-16531 HHH-18004 ColumnDefinitions should respect @Column(columnDefinition) #8137
base: main
Are you sure you want to change the base?
HHH-16531 HHH-18004 ColumnDefinitions should respect @Column(columnDefinition) #8137
Changes from all commits
0973c5a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works fine previously because
stripArgs
just keep string before(
, now it drop(*)
for keepunsigned
fromint(6) unsigned
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean, there really are a lot more possibilities than just
default
andnot null
. What aboutgenerated
? What aboutunique
? What aboutconstraint
?primary key
? etc, etc.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a really bad idea that
columnDefinition
allow mixing type and constrains, what's your suggestion here? writing a sophisticated parser or simply using substring to cover that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I 100% agree that it's bad.
columnDefinition
was a TopLink thing that I never really liked but at the time of JPA 1.0 didn't have a good reason to object to.As I've said, we need to support it because it's in the spec, but there's no requirement that migration/validation handle it elegantly.