You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2008/01/24 08:02:36 UTC
[jira] Commented: (OPENJPA-502) JPQL compliance setting
[ https://issues.apache.org/jira/browse/OPENJPA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561962#action_12561962 ]
Patrick Linskey commented on OPENJPA-502:
-----------------------------------------
This is now implemented with a new openjpa.Compatibility flag. To use:
openjpa.Compatibility: JPQL=[strict|warn|extended]
When set to 'warn', this will issue one warning per extended-syntax query per invocation in a particular EMF.
Currently, the extended-syntax recognized by this compatibility setting are scalar functions in the SELECT, GROUP BY, and ORDER BY clauses.
> JPQL compliance setting
> -----------------------
>
> Key: OPENJPA-502
> URL: https://issues.apache.org/jira/browse/OPENJPA-502
> Project: OpenJPA
> Issue Type: Sub-task
> Affects Versions: 0.9.0, 0.9.6, 0.9.7, 1.0.0, 1.0.1, 1.0.2
> Reporter: Patrick Linskey
> Fix For: 1.1.0
>
>
> Provide a configuration option to control JPQL compliance checks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.