Re: [eclipselink-dev] Possible bug with CriteriaBuilder

[Christopher Delahunt <christopher.delahunt@xxxxxxxxxx>]

This isn't a bug. When you pass true into your method it uses the following code

if (orderByAdvisorName) {
	criteria.orderBy(cb.desc(from.get("advisor").get("advisorName")));
	}

from.get("advisor") is causing an inner join as required by the spec.  You should reuse you left outer join instead:

criteria.orderBy(cb.desc(join.get("advisorName")));

Best regards

Chris

On May 20, 2017, at 6:22 PM, Jean Morissette <jean.morissette@xxxxxxxxx> wrote:

Hi dear EclipseLink developers,

I'm using EclipseLink (version 2.6.4) CriteriaBuilder API to build a left-outer-join with an order-by clause. However, it produces an inner-join query instead of a left-outer-join. 

You can take a look at this example to reproduce the problem: 

https://github.com/jean-morissette/JpaProvidersComparison/blob/master/src/test/java/JpaCriteriaBuilderTest.java

Hibernate produces the expected result.

Please, could you confirm it's effectively a bug, when it should be fixed and if a workaround exists in the meantime.

Thank you,

Jean

_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_eclipselink-2Ddev&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=xVpSyIIO_uKj1KAOMnm4_-T4KVw7uqAp5EeFOtyE4gI&m=wOxnLcXYVJ4mp1iVWDXqto33y58_qQaLd2mINUEj_0E&s=SMgp_B4QjosTKdjdCEpBxvJYZ-YFT6txK_5wyNrHmGM&e=