[
https://issues.apache.org/jira/browse/OPENJPA-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-939.
-------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: The standard JPQL TREAT(var AS
Subtype).field is now parsed (JPQL.jjt:565-568 treat_path) and tested
(persistence/jpql/treatjoinon/TestTreatSubclassDiscriminator), so the proposed
non-standard hint is no longer needed. Please reopen if this still happens with
OpenJPA 4.x.
> Allow query on subclass field on superclass extent under specific hint
> ----------------------------------------------------------------------
>
> Key: OPENJPA-939
> URL: https://issues.apache.org/jira/browse/OPENJPA-939
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Pinaki Poddar
> Priority: Major
>
> According to user [1], OpenJPA throws parse exception if JPQL on a superclass
> uses subclass field in path expressions.
> And, of course, the user reminds us that 'Hibernate can do it'.
> Given that it is not a kosher thing to do always, we should allow it only
> user sets subclass hints to true.
> [1]
> http://n2.nabble.com/%22No-field-named%22-problem-when-using-subclass-field-in-where-clause-tc2374779.html
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
