Re: [eclipselink-users] Change in Behavior in 1:1 Query from 2.3.1 to 2.

[christopher delahunt <christopher.delahunt@xxxxxxxxxx>]

Odd that this behavior changed as it was requested and rejected in bug 
246211.  I'm not sure why such a change would have been built into the 
parser except that it might have got included with 'ON' clause support, 
but I just might not have searched the bugs using the right criteria.

The workaround other than using the ANTLR parser is to force the inner 
join in the from clause:
  "select eHolders from Equipment o join o.equipmentHolders eHolders  
where o.entityId = 9000001"

I'd recommend filing a bug to at least help clarify the issue so it can 
be documented or changed back.


On 26/08/2014 9:25 AM, Rama Rao wrote:
> An update when we set the following property to switch back to the previous
> parser it worked fine.
> eclipselink.jpql.parser = org.eclipse.persistence.queries.ANTLRQueryBuilder
>
> I think it looks like the new Hermis parser is causing this. Could this be a
> bug?
>
> Thanks,
> Rama
>
>
>
> --
> View this message in context: http://eclipse.1072660.n5.nabble.com/Change-in-Behavior-in-1-1-Query-from-2-3-1-to-2-5-2-tp169617p169632.html
> Sent from the EclipseLink - Users mailing list archive at Nabble.com.
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users