Skip to content

duplicate persistent field names in hierarchy#945

Merged
gavinking merged 6 commits intojakartaee:mainfrom
gavinking:dupe-fields
Feb 24, 2026
Merged

duplicate persistent field names in hierarchy#945
gavinking merged 6 commits intojakartaee:mainfrom
gavinking:dupe-fields

Conversation

@gavinking
Copy link
Copy Markdown
Member

Update spec to address cases raised in #599.

@gavinking gavinking marked this pull request as ready for review February 5, 2026 13:24
@gavinking
Copy link
Copy Markdown
Member Author

@sebersole @mbellade does look right?

@gavinking gavinking added the 4.0.0 label Feb 5, 2026
Copy link
Copy Markdown
Contributor

@sebersole sebersole left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the semantics you define are logical. I do think the section could benefit from some sample code to help illustrate what is and is not supported.

@gavinking
Copy link
Copy Markdown
Member Author

OK, will do.

@gavinking
Copy link
Copy Markdown
Member Author

@sebersole I have added some examples. Is this what you were looking for?

Comment thread spec/src/main/asciidoc/ch02-entities.adoc
@gavinking gavinking linked an issue Feb 20, 2026 that may be closed by this pull request
@gavinking
Copy link
Copy Markdown
Member Author

I have generalized and simplified the restriction on duplicate column mappings.

@gavinking
Copy link
Copy Markdown
Member Author

Alright, I guess this clarification has had enough time to stew now, and three different people have reviewed. Time to merge it.

@gavinking gavinking merged commit 3dd6c92 into jakartaee:main Feb 24, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

duplicate persistent field names in hierarchy

4 participants