Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Examples/JPA/nonJDBCArgsToStoredProcedures"
< EclipseLink | Examples | JPA
(→How to specify nonJDBC arguments for Oracle Stored Procedures) |
|||
| Line 1: | Line 1: | ||
''{available as of EclipseLink 1.0M2}'' | ''{available as of EclipseLink 1.0M2}'' | ||
| − | == How to | + | == How to handle nonJDBC arguments for Oracle Stored Procedures == |
| + | |||
| + | The standard way of handling a Stored Procedure is to build an instance of <tt>oracle.toplink.queryframework.StoredProcedureCall</tt>. However, the arguments must be compatible with the JDBC specification. | ||
| + | |||
| + | To handle nonJDBC arguments (e.g. BOOLEAN, PLS_INTEGER, a new sub-class has been created: <tt>oracle.toplink.platform.database.oracle.PLSQLStoredProcedureCall</tt> | ||
Revision as of 12:26, 23 November 2007
{available as of EclipseLink 1.0M2}
How to handle nonJDBC arguments for Oracle Stored Procedures
The standard way of handling a Stored Procedure is to build an instance of oracle.toplink.queryframework.StoredProcedureCall. However, the arguments must be compatible with the JDBC specification.
To handle nonJDBC arguments (e.g. BOOLEAN, PLS_INTEGER, a new sub-class has been created: oracle.toplink.platform.database.oracle.PLSQLStoredProcedureCall