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) |
(→How to handle nonJDBC arguments for Oracle Stored Procedures) |
||
| Line 4: | Line 4: | ||
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. | 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> | + | To handle nonJDBC arguments (e.g. BOOLEAN, PLS_INTEGER, PL/SQL record, etc.) a new sub-class has been created: <tt>oracle.toplink.platform.database.oracle.PLSQLStoredProcedureCall</tt>: |
| + | |||
| + | For a target procedure: | ||
| + | <code><pre> | ||
| + | procedure bool_test(x IN BOOLEAN) | ||
| + | </code></pre> | ||
| + | |||
| + | x | ||
Revision as of 12:28, 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, PL/SQL record, etc.) a new sub-class has been created: oracle.toplink.platform.database.oracle.PLSQLStoredProcedureCall:
For a target procedure:
procedure bool_test(x IN BOOLEAN)
</code>
x