Column mapping fixes #7
Open
Conversation
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
lvojnovic
commented
Feb 26, 2015
lvojnovic
commented
- Multiple column unique constraint should list property names instead of column names (GPREVERSEENGINEER-15 GPREVERSEENGINEER-7 GPREVERSEENGINEER-23)
- Properties with names not converted from column names should have column mapping (usually foreign keys)
- When primary key is also a foreign key there needs to be (foreignKey insertable:false, updateable:false) in column mapping
When foreign key is also a primary key it causes a repeated column in mapping and an org.hibernate.MappingException. It is avoided with: "propName insertable:false, updateable:false"
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.