[GLASSFISH-481] add query hint to disable jpql validation Created: 27/Mar/06  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: entity-persistence
Affects Version/s: 9.0pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: tware Assignee: jielin
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 481

 Description   

There are some restrictions to jpql in the EJB 3.0 persistence specification
for the query language that disallow some things that will work on some
databases. As a result, JPQL validation will disallow writing queries that
could provide correct results on certain databases.

An example is: IN

From the spec:

in_expression ::=
state_field_path_expression [NOT] IN ( in_item

{, in_item}

* | subquery)
in_item ::= literal | input_parameter
The state_field_path_expression must have a string, numeric, or enum value

On an Oracle database IN can be used with Dates. With a hint to disable
validation, it would be possible to write a JPQL query that would correctly
return values that used an IN with a Date.



 Comments   
Comment by marina vatkina [ 27/Mar/06 ]

Reassigned

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Sun Apr 30 08:16:24 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.