Handle Composite id with IdClass annotation #1077
Labels
Comments
|
It's not a bug, there is no support for IdClass class in Javers. Consider contributing a PR with this new feature |
bala-striva
added a commit
to bala-striva/javers
that referenced
this issue
Mar 22, 2021
bartoszwalacik
added
fixed - waiting to be released
fixed & released
and removed
fixed - waiting to be released
labels
|
fixed in 6.0.0-RC2 |
lucas-prestes
pushed a commit
to lucas-prestes/javers
that referenced
this issue
Jun 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Clear description of my expectations versus reality
With Entities having an IdClass annotation and using other Entities as the id, Javers will use the toString of the id entity and not the id property. This could result in a very long InstanceId.
(See the linked test case for an example)
Steps To Reproduce
I have a **runnable test case ** which isolates the bug and allows Javers Core Team to easily reproduce it. I have pushed this test case to my fork of this repository:
bala-striva@803d6ae
Javers' Version
5.9.4-master
Additional context
With the dehydrate of the composite key values I was able to achieve that the InstanceId to contains only the referenced entities id field and not the toString representation of those entities.
The text was updated successfully, but these errors were encountered: