rss
SOATUBE
Oracle
Custom Search SOABYTE here

Monday, November 8, 2010

Stored Procedures Using Complex Types and the DEFAULT Clause

When working with stored procedures for which the Adapter Configuration wizard must generate wrapper SQL stored procedures, there is a current limitation on DEFAULT clauses not being carried over to the generated wrapper stored procedures.
As a workaround, perform the following steps one time only for a given stored procedure:
  1. Open the generated wrapper SQL script.
  2. Copy all default clauses from the base-stored procedure into the corresponding wrapper.
  3. Use SQL*Plus to reload the wrapper SQL script into the database.
  4. Edit the generated XSD. If a parameter has a DEFAULT clause, its corresponding element in the XSD must have the extra attribute: db:default="true"For example, with the following SQL:
    FINANCE$INVOICE(isTrue INTEGER DEFAULT 1, value NUMBER DEFAULT 0)
    The elements in the XSD for isTrue and value must have the new attribute:
    <element name="ISTRUE" ... db:default="true" .../>
    <element name="VALUE" ... db:default="true" .../> 

0 comments:

Post a Comment

 
Blogger Profile