Re: [eclipselink-dev] Check In Bug 330690 - Incorrect SQL when enum used

[Tom Ware <tom.ware@xxxxxxxxxx>]

I think this is a good suggestion to send the the spec committee.

-Tom

Goerler, Adrian wrote:
> Hi,
>
> I think the cleanest solution for this issue would be to add
>
> setParameter(String name, Enum<?> value, EnumType type) 
>
> and
>
> setParameter(int pos, Enum<?> value, EnumType type)
>
> to the Query interface (in JPA 2.1 ?).
>
> -Adrian
>
> Adrian Görler
> SAP AG
>
> Pflichtangaben/Mandatory Disclosure Statements:
> http://www.sap.com/company/legal/impressum.epx 
>
>
> -----Original Message-----
> From: eclipselink-dev-bounces@xxxxxxxxxxx [mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
> Sent: Dienstag, 11. Januar 2011 20:57
> To: Dev mailing list for Eclipse Persistence Services
> Subject: [eclipselink-dev] Check In Bug 330690 - Incorrect SQL when enum used as query parameter that does not reference a mapping
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=330690
>
> The fix defaults our behavior to use the ordinal number for an
> enumeration in the case where the segment of JPQL including the enum does not
> include a mapping.
>
> Reviewed by Chris Delahunt
>
> Added test to JUnitJPQLTestSuite and tested with JPA and Core LRG
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev