-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
Backport fix for #154 - @OrderBy on a @OneToMany property is not used when lazy loading #272
Conversation
…y loading Conflicts: src/main/java/com/avaje/ebeaninternal/server/deploy/BeanPropertyAssocMany.java src/test/java/com/avaje/tests/query/orderby/TestOrderByWithMany.java
Apologies for the delay. I was pondering the issues of backporting etc and at some stage just dropped the ball on this merge request. |
Backport fix for #154 - @orderby on a @onetomany property is not used when lazy loading
Any chance we could have a 3.3.3 release sometime soon? |
So what you'd like is just another release from the develop-v3 branch to go into maven central as 3.3.3. That is it right - or have I misunderstood? |
Yes, that would be perfect. We are using 3.3.2 and I'm reluctant to upgrade On Thu, Jun 18, 2015, 6:43 PM Rob Bygrave notifications@github.com wrote:
|
Ok, easy then - I should be able to release that this weekend, maybe tonight. |
Fantastic, and thank you for the rapid response! On Thu, Jun 18, 2015, 7:15 PM Rob Bygrave notifications@github.com wrote:
|
Thank you ! |
Ok, that has been released and is on it's way to maven central. Note that this release was version 3.4.2 (so not 3.3.3) - hopefully that is ok / expected your end. Cheers, Rob. |
great, we will give it a shot, thanks! On Fri, Jun 19, 2015 at 4:22 AM Rob Bygrave notifications@github.com
|
This fix is mainly for 3.3 branch (does not exists) which is used in Play Framework 2.3.x
Conflicts:
src/main/java/com/avaje/ebeaninternal/server/deploy/BeanPropertyAssocMany.java
src/test/java/com/avaje/tests/query/orderby/TestOrderByWithMany.java