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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

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

From: Rama Rao <ramaraochavali@xxxxxxxxx>
Date: Tue, 26 Aug 2014 06:25:10 -0700 (PDT)
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>

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.

Follow-Ups:
- Re: [eclipselink-users] Change in Behavior in 1:1 Query from 2.3.1 to 2.5.2
  - From: christopher delahunt

References:
- [eclipselink-users] Change in Behavior in 1:1 Query from 2.3.1 to 2.5.2
  - From: Rama Rao

Prev by Date: [eclipselink-users] Change in Behavior in 1:1 Query from 2.3.1 to 2.5.2
Next by Date: Re: [eclipselink-users] Change in Behavior in 1:1 Query from 2.3.1 to 2.5.2
Previous by thread: [eclipselink-users] Change in Behavior in 1:1 Query from 2.3.1 to 2.5.2
Next by thread: Re: [eclipselink-users] Change in Behavior in 1:1 Query from 2.3.1 to 2.5.2
Index(es):
- Date
- Thread

Breadcrumbs