Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> dbms_sql.parse

dbms_sql.parse

From: Anders Eriksson <anders_at_knowledgepartner.com>
Date: Sat, 27 Feb 1999 23:58:10 +0100
Message-ID: <36D87882.5AC7315A@knowledgepartner.com>


Hello!

I have discovered that dbms_sql.parse have two different formats. When I use the first format the procedure works fine but when I try the other I can not get it to work. It seems like it still tries to use the first format and therefore is complaining about the wrong type of parameters.

Have anyone any idea how to get the second format to work?

FORMAT 1: PROCEDURE PARSE

 Argument Name                  Type                    In/Out Default?

------------------------------ ----------------------- ------ --------
C NUMBER(38) IN STATEMENT VARCHAR2 IN LANGUAGE_FLAG NUMBER(38) IN FORMAT 2: PROCEDURE PARSE Argument Name Type In/Out Default?
------------------------------ ----------------------- ------ --------
C NUMBER(38) IN STATEMENT TABLE OF VARCHAR2(256) IN LB NUMBER(38) IN UB NUMBER(38) IN LFFLG BOOLEAN IN LANGUAGE_FLAG NUMBER(38) IN dbms_sql.parse( myCursor, sqlStatement, dbms_sql.native ); -- OKEY
dbms_sql.parse( myCursor, sqlStatementTable, 1, 16, TRUE, dbms_sql.native ); -- Gives the folowing error

LINE/COL ERROR




43/3 PLS-00306: wrong number or types of arguments in call to 'PARSE'
43/3 PL/SQL: Statement ignored

Where sqlStatementTable defined as:
table of varchar2(256)
 index by binary_integer;

Regards
Anders Eriksson


Received on Sat Feb 27 1999 - 16:58:10 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US