Remove @MapsId from ResourceGroupImage to fix composite key coupling #158
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.
@MapsIdcreates bidirectional coupling between the embedded composite key and relationship associations, causing JPA mapping conflicts in entities with@EmbeddedId.Changes
@MapsIdannotations fromresourceGroupandcontainerImageassociationsinsertable=false, updatable=falseon@JoinColumnidin constructor when both entities are provided:@PrePersistguard as safety mechanismThe embedded ID now controls FK columns exclusively, eliminating mapping ambiguity while maintaining proper entity relationships.
Original prompt
This pull request was created as a result of the following prompt from Copilot chat.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.