You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Andrus Adamchik (JIRA)" <ji...@apache.org> on 2012/06/27 19:29:44 UTC
[jira] [Created] (CAY-1715) Passing parameters to mapped EJBQL
queries
Andrus Adamchik created CAY-1715:
------------------------------------
Summary: Passing parameters to mapped EJBQL queries
Key: CAY-1715
URL: https://issues.apache.org/jira/browse/CAY-1715
Project: Cayenne
Issue Type: Bug
Components: Core Library
Affects Versions: 3.1B1
Reporter: Andrus Adamchik
Per http://markmail.org/message/rfedwacpttzxhpbz we need to make sure that EJBQLQueries mapped in the Modeler can accept parameters when run as a NamedQuery. It looks like an oversight on our part. I guess positional parameters can not be supported by the current NamedQuery API (may need to jira that as a feature request), but named parameters most certainly should.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (CAY-1715) Passing parameters to mapped EJBQL
queries
Posted by "Olga Tkacheva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAY-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olga Tkacheva closed CAY-1715.
------------------------------
Resolution: Fixed
Fix Version/s: 3.1B2
fixed
> Passing parameters to mapped EJBQL queries
> ------------------------------------------
>
> Key: CAY-1715
> URL: https://issues.apache.org/jira/browse/CAY-1715
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
> Affects Versions: 3.1B1
> Reporter: Andrus Adamchik
> Assignee: Olga Tkacheva
> Fix For: 3.1B2
>
>
> Per http://markmail.org/message/rfedwacpttzxhpbz we need to make sure that EJBQLQueries mapped in the Modeler can accept parameters when run as a NamedQuery. It looks like an oversight on our part. I guess positional parameters can not be supported by the current NamedQuery API (may need to jira that as a feature request), but named parameters most certainly should.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAY-1715) Passing parameters to mapped EJBQL
queries
Posted by "Olga Tkacheva (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAY-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olga Tkacheva reassigned CAY-1715:
----------------------------------
Assignee: Olga Tkacheva
> Passing parameters to mapped EJBQL queries
> ------------------------------------------
>
> Key: CAY-1715
> URL: https://issues.apache.org/jira/browse/CAY-1715
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
> Affects Versions: 3.1B1
> Reporter: Andrus Adamchik
> Assignee: Olga Tkacheva
>
> Per http://markmail.org/message/rfedwacpttzxhpbz we need to make sure that EJBQLQueries mapped in the Modeler can accept parameters when run as a NamedQuery. It looks like an oversight on our part. I guess positional parameters can not be supported by the current NamedQuery API (may need to jira that as a feature request), but named parameters most certainly should.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira