[
https://issues.apache.org/jira/browse/OPENJPA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-277.
-------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: A broad wish with no concrete
design. StoredProcedureQuery, native queries and custom
FieldStrategy/ClassStrategy now cover the practical cases. Please reopen if
this still happens with OpenJPA 4.x.
> Provide a simple means for manual specification of all SQL used by a given
> domain graph
> ---------------------------------------------------------------------------------------
>
> Key: OPENJPA-277
> URL: https://issues.apache.org/jira/browse/OPENJPA-277
> Project: OpenJPA
> Issue Type: New Feature
> Components: jdbc
> Affects Versions: 0.9.0, 0.9.6, 0.9.7
> Reporter: Patrick Linskey
> Priority: Major
> Attachments: OPENJPA-277.patch
>
>
> Generally-speaking, OpenJPA generates the SQL needed to load records from the
> database. Currently, the only mainstream exception to this is when using SQL
> as a query language.
> In legacy environments, database access is often limited to certain SQL
> statements or stored procedures. OpenJPA should support such environments for
> a larger subset of OpenJPA operations.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
