-
Notifications
You must be signed in to change notification settings - Fork 54
EmbeddedId management #62
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
Conversation
@ludovicmotte Thank you very much for your PR! I really dig the feature to enable support for The where criteria expression schema should only enable using
This test fails with the following exception:
|
Codecov Report
@@ Coverage Diff @@
## master #62 +/- ##
============================================
+ Coverage 60.4% 62.37% +1.96%
+ Complexity 283 269 -14
============================================
Files 31 21 -10
Lines 1816 1632 -184
Branches 282 253 -29
============================================
- Hits 1097 1018 -79
+ Misses 593 508 -85
+ Partials 126 106 -20
Continue to review full report at Codecov.
|
@ludovicmotte There could be other use cases where embedable ids criteria expressions could be more comlex, i.e.
What do you think? Is it something that could be useful? The EQ use case could be expressed as follows:
|
@igdianov Thanks for the review, I understand your point.
What do you think about it ? It can also cover your complex criteria expressions. To sum up:
You can see the fix of pr/62/merge in my repo. Best regards, |
@ludovicmotte I like your proposal to use reverse query syntax with where in query field for |
Oups, I closed my pull request without knowing it, but I still want to contribute !
Is it what you were exepecting ? |
NB : your sample application seems not to work anymore:
|
Hi,
This is a new feature : managing JPA @EmbeddedId
Best regards.